Method and system for importing MS office forms

ABSTRACT

Collaboration space object model provides for a place consisting of rooms created by users interacting with a client browser. A skin (i.e., theme) may be used as template for creating places. PlaceBots (i.e., agents) provide for accessing, processing and managing data in a place. HTML may be dragged and dropped into a place, where it is parsed and corresponding place fields created. MS Excel or Word documents may be dragged and dropped into a place, which creates a corresponding form, and users may create new documents using that form. A place type comprising a template of an entire place, or collaboration space, may be used to create new places. Changes made to a place may be reported, subject to security controls, by selecting what&#39;s new. Task fields are provided allowing web browser creation of forms for work flow. Place enabled objects are provided for synchronous communications. A quick browse feature provides a simplified format for browser windows based on selection of HTML links. MS Office documents may launched within a place for in place editing and importing the resulting document into the place.

CROSS REFERENCES TO RELATED APPLICATIONS

The following U.S. patent applications, filed concurrently herewith, areassigned to the same assignee hereof and contain subject matter relatedto the subject matter of the present application.

U.S. patent application Ser. No. 09/752,120, filed 29 Dec. 2000,entitled “Method and System for Creating a Theme of a Place to be Usedas a Template for Other Places”;

U.S. patent application Ser. No. 09/752,115, filed Dec. 29, 2000,entitled “Method and System for Automatically Accessing, Processing, andManaging the Data In a Place”;

U.S. patent application Ser. No. 09/752,121, filed Dec. 29, 2000,entitled “Method and System for Importing HTML Forms”;

U.S. patent application Ser. No. 09/752,942, filed Dec. 29, 2000,entitled “Method and System for Creating a Place Type to Be Used as aTemplate for Other Places”;

U.S. patent application Ser. No. 09/752,934, filed Dec. 29, 2000,entitled “Method and System for Identifying and Displaying InformationThat Is New or Has Been Updated In a Place”;

U.S. patent application Ser. No. 09/752,961, filed Dec. 29, 2000,entitled “Method and System for Providing Task Information in a Place”;

U.S. patent application Ser. No. 09/752,745, filed Dec. 29, 2000,entitled “Method and System for Providing Synchronous Communication andPerson Awareness In a Place”;

U.S. patent application Ser. No. 09/752,962, filed Dec. 29, 2000,entitled “Method and System for Providing a Separate Browser Window withInformation From the Main Window In a Simpler Format”;

U.S. patent application Ser. No. 09/752,935, filed Dec. 29, 2000,entitled “Method and System for Allowing In Place Editing of OfficeDocuments In a Place”.

The present application is also an improvement upon the followingcopending, previously filed applications, assigned to the same assignee:

U.S. patent application Ser. No. 09/473,745, filed 28 Dec. 1999,entitled “System and Method for Interconnecting Secure Rooms”;

U.S. patent application Ser. No. 09/473,630, filed 28 Dec. 1999,entitled “System and Method for Dynamic Management of Web Site”;

U.S. patent application Ser. No. 09/473,640, filed 28 Dec. 1999,entitled “System and Method for Presentation of Room Navigation”;

U.S. patent application Ser. No. 09/473,098, filed 28 Dec. 1999,entitled “System and Method for Independent Room Security Management”;

U.S. patent application Ser. No. 09/477,477, filed 4 Jan. 2000, entitled“System and Method for Dynamically Generating Viewable Graphics”;

U.S. patent application Ser. No. 09/477,471, filed 4 Jan. 2000, entitled“System and Method for Dynamic Browser Management of Web Site”;

U.S. patent application Ser. No. 09/477,474, filed 4 Jan. 2000, entitled“System and Method for Room Decoration and Inheritance”;

U.S. patent application Ser. No. 09/477,469, filed 4 Jan. 2000, entitled“System and Method for Online/Off line Uninterrupted Updating of Roomsin Collaboration Space”;

U.S. patent application Ser. No. 09/477,473, filed 4 Jan. 2000, entitled“System and Method for Client Replication of Collaboration Space”;

U.S. patent application Ser. No. 09/477,476, filed 4 Jan. 2000, entitled“System and Method for Browser Creation and Maintenance of Forms”; and

U.S. patent application Ser. No. 09/478,238, filed 4 Jan. 2000, entitled“System and Method for Browser Definition of Workflow Documents”.

The above-identified patent applications are incorporated herein byreference.

TECHNICAL FIELD OF THE INVENTION

This invention relates to web technology. More particularly, it relatesto the creation and use of collaboration sites on the Internet or on anIntranet client/server system and to the graphical user interface usedin Internet communications.

BACKGROUND ART

The Internet and the World Wide Web (WWW) provide intra-enterpriseconnectivity, inter-enterprise connectivity and application hosting on alarger scale than ever before. By exploiting the broadly available anddeployed standards of the Internet and the WWW, system users anddesigners can leverage a single architecture to build client/serverapplications for internal use that can reach outside to customers,business partners and suppliers.

Collaboration requires simultaneous communication between individuals ona project team. Typically, this has required that the team members workin the same location. Phone and video conferencing has enabled someremote work on the part of team members. Also, because of the growth ofthe Internet, collaboration using web technologies has been attempted,primarily using electronic mail (E-mail), Internet chat rooms,electronic whiteboards, and conferencing software. The most useful hasbeen E-mail, but this approach results in a large trail or thread ofnotes as collaboration on a project advances, and these notes have nohome or place to reside which is accessible by all team memberssubstantially instantaneously and simultaneously. People often entersuch a thread at different points, and such threads are not efficient incoordinating the work of many different people on a team which mayinclude in-house developers and others, such as remote contractors,outside of an enterprise's firewall.

In order for such disperse teams to have the same, or substantially thesame, collaboration environment as individuals working in the samephysical office, a system is required which facilitates instantmessaging, voice conferencing, electronic white boarding, and text andnon-text file exchange. Such a system needs to provide a collaborativeelectronic room, or space, which is easily configured for use by teammembers without substantial administrative or application developmentsupport, and preferably include both groupware and project orientedapplications such as shared folders, file exchange, workflow, groupcalendars, threaded conversations, version control, file locking, filemerging, and security.

There is a need in the art for such a system which is easy to set up andwhich enables diverse and remote teams to become immediately productivein a secure environment. It would be, further, most desirable to allowsuch a collaborative environment to be set up without administrativesupport, that is by members of the team itself, using a familiar andeasy to use browser user interface. Members of the team, acting withmanager or author authority, and using such a browser interface withoutinvolving administrative or application development support, need to beable to set up a folder or room for each project element, such as asource code component, with version control, workflow elements, andgroup calendaring for tracking the project or project element withrespect to approvals and deadlines. Such a room needs to receive fromteam members reports and have them routed to appropriate team membersfor review, resolution, and approval.

The WWW is a collection of servers on an IP (Internet Protocol) network,such as the Internet, an Intranet or an Extranet, that utilize theHypertext Transfer Protocol (HTTP). Hereinafter, “Internet” 100 will beused to refer to any IP network.

HTTP is a known application protocol that provides users with access tofiles, which can be in different formats, such as text, graphics,images, sound, and video, using a standard page description languageknown as Hypertext Markup Language (HTML). Among a number of basicdocument formatting functions, HTML allows software developers tospecify graphical pointers on displayed web pages, commonly referred toas “hyperlinks,” that point to other web pages resident on remoteservers. Hyperlinks commonly are displayed as highlighted text or othergraphical image on the web page. Selection of a hyperlink with apointing device, such as a computer mouse, causes the local computer todownload the HTML associated with the web page from a remote server. Thebrowser then renders the HTML into the displayed web page.

Web pages accessed over the Internet, whether by a hyperlink, openingdirectly via an “open” button in the browser, or some other means, arecommonly downloaded into the volatile cache of a local computer system.In a computer system, for example, the volatile cache is a high-speedbuffer that temporarily stores web pages from accessed remote web sites.The volatile cache thus enables a user to quickly review web pages thatwere already downloaded, thereby eliminating the need to repeat therelatively slow process of traversing the Internet to access previouslyviewed web pages. This is called local caching.

It is an object of the invention to provide a collaboration spaceapplication model for creating web applications that are aestheticallypleasing and present the user with a simple interface.

It is a further object of the invention to provide for creating webapplications that are instantly created, instantly archived, team andproject oriented, easy to use, created, accessed and administered viathe Web, reusable, and extensible.

It is a further object of the invention to provide an improved methodand system for uploading Microsoft Office documents, presentations andsheets into a place in collaboration space.

SUMMARY OF THE INVENTION

In accordance with the invention, there is provided a method and systemfor uploading a document into a place in collaboration space, bycreating a document file including web form fields; saving the documentfile; importing the document file to the place; and upon importing thedocument into the place, converting the document into a web filecontaining hyperlinks that point to web pages.

In accordance with an aspect of the invention, there is provided acomputer program product configured to be operable for uploading adocument into a place in collaboration space, according to the steps ofcreating a document file including web form fields; saving the documentfile; importing the document file to the place; and upon importing thedocument into the place, converting the document into a web filecontaining hyperlinks that point to web pages.

Other features and advantages of this invention will become apparentfrom the following detailed description of the presently preferredembodiment of the invention, taken in conjunction with the accompanyingdrawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic representation of a typical server/client systemimplementing the collaboration space of the preferred embodiments of theinvention.

FIG. 2 is a schematic representation of various server and clientcomponents implementing the collaboration space of the preferredembodiments of the invention.

FIG. 3 is a schematic map illustrating Domino objects relating to theobject model of the collaboration space of the preferred embodiments ofthe invention.

FIG. 4 is a schematic map of the object model implementing thecollaboration space of the preferred embodiments of the invention.

FIG. 5 illustrates the components of a collaboration space userinterface.

FIG. 6 is a flow chart representation of generation of collaborationspace data objects.

FIG. 7 illustrates a typical collaboration space user interface.

FIG. 8 is a schematic representation of a directory structure, alongwith the files in an exemplary collaboration space server.

FIG. 9 is a flow chart representing the method steps for creating aPlaceBot.

FIG. 10 is a schematic representation of a screen capture illustratingcreation of a new page in accordance with a preferred embodiment of theinvention.

FIG. 11 is a schematic representation of a screen capture illustratingthe user interface for creating a new page in collaboration space.

FIG. 12 is a schematic representation of a screen capture illustratingthe user interface for in Place editing of Microsoft documents.

FIG. 13 is a flow chart illustrating in-place editing in accordance withthe preferred embodiment of the invention.

FIG. 14 is a schematic representation of a screen capture illustratingthe user interface for in Place editing of Microsoft documents.

FIG. 15 is a schematic representation of a screen capture illustratingthe user interface for attaching forms.

FIG. 16 is a system diagram illustrating importing interest content intocollaboration space.

FIGS. 17-20 are schematic representations illustrating the userinterface for editing a collaboration space file attachment and savingthe changes back to collaboration space.

FIG. 21 is a flow chart illustrating the creation and importation intocollaboration space of a form.

FIG. 22 is a schematic representation of a task page presented in listmode.

FIG. 23 is a schematic representation of a task page presented in timeline mode.

FIG. 24 is a schematic representation of a read scene state display fortasks.

FIG. 25 is a schematic representation of a user interface forintegrating a form into workflow.

FIG. 26 is a schematic representation of a user interface for addingevents to a calendar page and for publishing it in a specific folder incollaboration space.

FIG. 27 is a schematic representation of a user interface includingupload control.

BEST MODE FOR CARRYING OUT THE INVENTION Architecture Overview

Referring to FIG. 1, a broad overview of a system implementing thecollaboration space technology of an exemplary embodiment of the systemof the invention is presented.

Server 100 includes a Domino server 104, HTTP server 106, QuickPlaceextensions 108, and open storage 130. Client 102 includes a QuickPlaceuser interface 110 and browser 112.

QuickPlace open storage 130 includes all the databases and templatesthat implement the collaboration space. Domino 132 and active directory134 define the collaboration process. The user interfaces with thesystem through browser 112. .NSF agents 114, 116, Java 118 andLotusScript 120 represent components and templates downloaded fromserver 100 in support of collaboration space at client 102. All theextensions 108 are keyed off the URL, as will be further explainedhereafter.

Notes API 136, Notes designer 138 and client 140, external applications142, including Java agents 144 and LotusScript 146, are located off ofopen storage 130. Open storage 130 is storage where a document can becommunicated, such that external applications 142 may manipulate it.QuickPlaces, pages, folders, can be created and changed, and data 148can be imported and exported, using agents in Java 144 or LotusScript146.

QuickPlace is primarily concerned with representing the collaborationspace. Consequently, designers and consultants are able to integrateinto that space custom features and data from other applications. HTMLforms 122, written using an HTML editor 124, skins 248 (HTML 244 and QPtags), external files written using Java 118, and MS office documents250 from MS office 228, may be imported to server 100 by dragging anddropping 111 from local storage 502 into an upload control panel 240 inbrowser 112.

An alternate client 126 and encapsulated place types 128 may be providedfrom which other spaces 129 can be created that take advantage of theQuickPlace storage model, providing functionality which can bemanipulated using browser 112, including the integration of externaltechnology providing opportunity for deep customization.

Server/Client Components

Referring to FIG. 2, in accordance with an exemplary embodiment of theinvention, several components comprise QuickPlace server 100 and client102.

QuickPlace is built on top of the Domino server 104. In the case of astand alone installation, a subset of the Domino server is installed.Server 100 also includes HTTP server 106, or the optional MS IIS server150. QuickPlace extension 108 is where we built most of thecollaboration space implementing code exists the server 100. Server 100also includes a spell checker 152 and a text to GIF converter(Limerick).

Client 102 includes rich text edit control 162, and applet 164 withwhich to apply various attributes and is a key component of theQuickPlace experience. Upload control 166 is used to attach and uploadfiles, such as bringing in an agent and uploading it to a place. This isalso used to bring in an imported HTML form or a different skin. Uploadcontrol is implemented to allow ease of use via drag and drop. Javascript 118 includes code downloaded to the client to complete thegeneration of HTML pages.

Collaboration Space Object Model

Referring to FIG. 3, the collaboration space of the preferred embodimentof the invention, referred to as QuickPlace, is implemented with anobject model which comprises very few objects, very few concepts inorder to make it easy to build and manage. And the fewer concepts, thebetter.

Referring to FIG. 3, the object model is independent of itsimplementation. There exists a place 172 that has rooms 174, and thereare pages 182 in those rooms. And then there are members 190 of theplace. Those four objects 172, 174, 182 and 190 are the primary objects.

Folders 176 add more complexity to the model, but bring a lot of benefitas well. Pages 182 are organized within folders. Two further objects areprimarily visible to the designer of the place. And these are forms 178and fields 180.

Place type 196 is a more advanced object, and is an object from which aplace 172 is created. Place type 196 represents the foundation forbuilding true collaborative applications. Everything created in buildingcollaboration space is done in a place 172. Once such a place iscreated, it can be made a template 266 (FIG. 6) and copied as a placetype 196. Once it becomes a place type 196, it is available for use byothers for building additional places 172 that include the format, lookand feel, and other characteristics of the original place.

This is illustrated in FIG. 11, where a first place 360 is converted byQP extensions 108 into a place type, or template 364 from whichadditional places 366 may be created.

Room type 198 is an object provided for creating rooms 174 which are ofa given type.

The last two objects illustrated in FIG. 3 are skins 200 and PlaceBots184. Skins 200 control everything about the user interface, includinglayout and style. Layout defines the positioning of components on thescreen. Style defines the form and colors of those components. APlaceBot 184 is an enhanced agent, enhanced in the sense that it enablesthe use of Java or Lotus Notes or equivalent text editors. Once writtenusing such an editor, and uploaded to a place 172, the server compilesthe PlaceBot into an agent, reporting any errors. The agent resultingfrom a compiled PlaceBot can be scheduled to run at certain times, orupon opening a form. That is, the PlaceBot may be associated with aform, such as a sales order which, when opened, will cause the agent toexecute. Thus, PlaceBots 184 are an essential part of buildingcollaboration applications, for they are the primary repository forcustom logic.

Referring further to FIG. 3, a preferred implementation of the objectmodel heretofore described uses Lotus Notes/Domino concepts and objects.Thus, Notes/Domino file system directory 202 represents place 172;database 204 represents room 174; folder view 206 represents folder 176;pages 182, members 190, forms 178, fields 180 and skins 200 arerepresented by notes 208, 210, 212, 214, 220, respectively.

Place 172 is represented as a file system directory. So whenever a placecalled Acme is created, a file system directory 202 called Acme will beinstantiated. Within that directory 202, there are a number of objects.Each room 174 is a Notes database 204. Folders 176 are implemented asNotes folders or views 206 depending on what's more convenient for theparticular folder.

Pages 182 are a combination of data notes, forms and sub-forms 208. Amember 190 is a data note 190 in a context room 174. Forms 178 andfields 180 are data notes. Place type 196 is a directory* 216 thatcontains all the rooms 174 that make up that place type. A room type 198is a template 218. Skins 200 are a note 220 and PlaceBot 184 is an agent222.

Notes/Domino Implementation of the Object Model

Developers familiar with the Domino Object Model (Domino OM) will beable to leverage their existing skills when developing on the QuickPlaceplatform. “PlaceBots” for example are implemented as Domino Agents, andit is possible to create and test them on Domino Databases. Within theQuickPlace object model (OM), however, there are some divergences fromthe Domino OM. For example, QuickPlace forms 178 are not the same asDomino Forms. QuickPlace forms more closely resemble Domino Documents,because they are created using a Domino form, and contain a Domino textfield with a value of “h_Form”. The value of “h_form” tells QuickPlacethat this Domino document should be rendered in a browser as aQuickPlace form 178.

This structure provides flexibility for Web applications with lesscomplexity than if Domino Forms were used. For example, in a defaultQuickPlace, a user can create a new QuickPlace form 178. The userchooses which fields to include in form 178, in what order they shouldappear and what text and or graphics should appear near them. To createthis sort of instant structure on the Web using Domino Forms would bevery complex indeed. QuickPlace has extended this concept of being ableto use HTML to define forms 178 by enabling the creation of customQuickPlace forms using imported HTML 122. These Forms not only make useof Web authoring technologies such as JavaScript, but also have the backend support of Domino. This back end logic is implemented via tools suchas PlaceBots (Domino Agents) 184. This means that forms 178 have theability to not only to define the look and feel of visible parts of anapplication, they also have the potential to initiate workflow and manyother powerful automated features.

QuickPlace forms 178 have been optimized by stripping away many of theNotes features not required when used on the Web. A another advantage ofthis structure is that it enables the use of Web authoring tools toextend the objects. For example, with respect to QuickPlace forms, it ispossible to modify forms using XML, JavaScript and HTML and any otherWeb tools. Knowledge of JavaScript and HTML are more common than DominoDesigner skills, thus making the QuickPlace a very open platform. Someparts of the QuickPlace OM implement Domino/Notes functionality indifferent ways to a standard Domino application. For example, QuickPlaceuses Domino's security and authentication model as a basis for itsmanagement of access to QuickPlaces. However, instead of primarilyutilizing the Domino Directory, QuickPlace also uses a Contacts1.nsfdatabase for each QuickPlace.

Containment and Association of Objects

Referring to FIG. 4, this object model is further described. FIG. 4illustrates selected QuickPlace objects, the directory structure and howObjects relate to each other within the hierarchy. This model provides avisual representation of the containment and association betweenobjects.

QuickPlace Server

The highest level of the model is the QuickPlace Server 170. Withinserver 170 are all of the QuickPlaces 172 as well as the resources theyaccess to finally render Web applications.

This FIG. 4 displays the Model focusing on QuickPlaces. The followingexplanation, written from a programmers perspective, describes each ofthe objects of the model and they can be accessed in an application.

QuickPlace uses notes for many of its objects 182, 190, 178, 180 and200, so that objects in the Place can be organized more easily. Table 1sets forth the QP objects and their Notes/Domino equivalents. As anexample of how design Notes are implemented consider the Table OfContents (TOC). The Table Of Contents is a list of pages, folders andtools such as the Customize Area. Domino Folders may be listed using alink document, or Note.

TABLE 1 QUICKPLACE OBJECTS AND DOMINO EQUIVALENT QuickPlace ObjectDomino Equivalent QuickPlace Server File Directory Place File DirectoryPage Data Note, Form & Subform PlaceBot Domino Agent Theme Data NoteMember Data Note in Contacts1.nsf Subroom* NSF Database SubroomThemeData Note SubroomMember Data Note in Contacts1.nsf Room NSF DatabaseFolder/TOC Folder or View Form Data Note Field Data Note *Subroomscontain their own set of Folder, Page, Form, Field, PlaceBot & SubroomObjects

QuickPlace Server 170 is a file directory containing all Places andResources. The Domino equivalent is a file directory 202 named“quickplace”. This identifies the main folder 176 for a QuickPlaceserver 170. If the QPServer 170 is running as a stand alone, this folderwill be in the QuickPlace data folder. For example

D:\QuickPlace\Data\quickplace.

If the QPServer 170 is running on top of a Domino server the folder willbe the Domino Data folder. For example

D:\Lotus\Domino\Data\quickplace.

To locate QuickPlace Server 170 in PlaceBots and get access to all ofits databases, a LotusScript method GetDbServer is executed togetherwith a test that the Path to databases starts with “QuickPlace”.

Place Object

Place object 172 is a directory in the “QuickPlace” directory groupingresources for a Place. The Domino equivalent is a file directory bearingthe name of the QuickPlace. Place object 172 is a directory that bringstogether a Place for organizational purposes. It also identifies theNSFs 114 as belonging to the place 172 by bearing the name of theQuickPlace. As distinguished from a place object 172, the main room 174in a QuickPlace is a database called Main.nsf. Place object 172 groupsand identifies the Main.nsf resources for the Place and any subrooms 194in the Place. Place object 172 contains several files. There is aMain.nsf, Contacts1.nsf and a Search.nsf file. If the QuickPlace has aSubroom 194 there will also be an NSF file with its name starting with“PageLibrary”. Each of these page library files is a Room 174.

The place object in PlaceBots 184: place object (directory) 172,contains the databases which form a place. When writing PlaceBots, onecan search for this directory by using the name of the QuickPlace. Inthis directory will be found all the databases will belong to that place172. This file directory's name is the name of the QuickPlace. Forexample, if the QuickPlace is called “Millennia”, this directory has thefollowing path within the QuickPlace server 170:

\millennia

To find the place object 172 for the Millennia Place in LotusScript thescript procedure of Table 2 may be used:

TABLE 2 SCRIPT PROCEDURE FOR FINDING A PLACE Dim ndbPlace AsNotesDatabase Set dirPlace = New NotesDbDirectory( g_sServerName ) SetndbPlace = dirPlace.GetFirstDatabase( DATABASE ) sNdbPlaceFilepath =ndbPlace.FilePath If Instr(1, Lcase( sNdbPlaceFilepath ),|quickplace\millennia| ) Then ‘//the Place is found

Room Object

Room object 174 is the main container for a Place, containing acollection of pages and tools. The Domino Equivalent an NSF Database.The room 174 is the main container for a QuickPlace's content. Forexample, when using the Millennia Place, most of what is seen iscontained in the Room object. The Room object is always called Main.nsf,and holds folders 176 and pages 182 for the QuickPlace, as well asmanaging links to any subrooms 194 in the place object 172. Room object174 uses elements held in other databases. For example many of thestandard images QuickPlace displays are in a resources object (notshown). Each room 174 has its own security and authentication, and theinformation required to do this is contained in databases such asContacts1.nsf. A room 174 breaks down a place 172 into smaller areas tohelp define structure. Each room 174 has its own security andauthentication. This allows separate user groups. It also means thatsubrooms 194 can be created for separate projects, forming a separateshared space. The room object 174 then forms a common entry point whereshared resources can be stored.

The room object in PlaceBots: to locate a room 174, one looks in themain QuickPlace Server 170 directory, then looks into the room object (adirectory bearing the name of the QuickPlace), then looks for a databasecalled “Main.nsf”.

Returning to previous LotusScript example of locating a Place 172 (Table2), the match string can be extended from

“quickplace\millennia” to

“quickplace\millennia\main.nsf”

to find the room object 174, as set forth in Table 3.

TABLE 3 SCRIPT PROCEDURE TO FIND A ROOM OBJECT Set dirPlace = NewNotesDbDirectory( g_sServerName ) Set ndbPlace =dirPlace.GetFirstDatabase( DATABASE ) sNdbPlaceFilepath =ndbPlace.FilePath If Instr(1, Lcase( sNdbPlaceFilepath ),|quickplace\millennia\main.nsf| ) Then ‘//the Room id found.

To access elements contained in a room 174, the views and folders 176 inthe room are accessed. For example to find the elements visible in theTable Of Contents (TOC), the “h_TOC” view is used.

The Room object 174 in HTML is visible in URLs as the “main.nsf”. Toaccess room object 174 most easily, a relative path is used from thecurrent object if it is in the same Place 172. For example, whencreating a URL link from a subroom 194 to a room 174, the URL begins asfollows:

<a href=“../../Main.nsf/

where the “dot dot slash dot dot slash” syntax is a part of the URL, notan abbreviation for this example. Using this relative URL makes the URLmore robust. In other words, this URL can be used to find the (Main.nsf)room 174 for any place 172.

Room fields 180 used to define rooms 174 are set forth in Table 4.

TABLE 4 FIELDS DEFINING ROOMS Field Name Description h_HaikuName Thename of this Place h_AreaType The name of the template used to createthis room. h_AreaParent The name of the parent database h_ShowSecurityIf h_SetSecurity = 1, the QuickPlace server sets h_ShowSecurity to 1.h_SetCalendar Determines if the Calendar will be visible in a Room. Ifthe field has the value of “1” a link to the Calendar will be displayedin the sidebar h_SetSecurity This field works in conjunction with theh_ShowSecurity field. It is only valid for Readers and Authors, becauseManagers must always be able to edit security of a Room. If the field isset to “1” a link to the Security page will be displayed in the sidebarfor Readers and Authors (if they select Security in this case they willsee only their own information) h_MailDb The name of the database thatreceives email addressed to this Place.

Folder Object

A folder object 176 is an object for indexing content, grouping relatedpages 182, and dividing a room 174 into sections without imposing newsecurity. The Domino equivalent is Notes folder or view 206, and Notesfolders 206 have three functions. For the user, they provide a logicalgrouping of related documents. This makes it easier for the user to finddocuments, and allows people with a shared interest to work an area of aQuickPlace. The other way of using folders is in the user interface, or“User” folders. Within user folders there are seven different types:

1. Standard List

2. Headline

3. Slide Show

4. Response List

5. Ordered List

6. Table Of Contents

7. Index

Folder types 1 to 5 are all available as styles for new, custom folders.From the a site manager's perspective, a Folder allows a QuickPlace tobe divided into areas for separate groups of people, without having tobe concerned about access control which would be necessary if a Subroom194 were used.Fields include the following:

-   “h_LastAttachmentDirectory”: used when getting attachments.    This field enables users to quickly upload attachments. For example,    each time a Layout file is uploaded, QuickPlace knows where to go    looking for the file. This path information is sourced from this    field.-   “h_DirtyAesthetics Number”: indicates which items should be checked    (once a part of the aesthetics has been tweaked, a check mark    indicates that the part has been changed).-   h_AreaHasAesthetics: indicates if a Room has its own aesthetic    settings enabled. If the field value is “1” the Room has had the    aesthetics tweaked.

The third way that folders 176 are used is to allow developers to locateelements in a QuickPlace. To a developer, folders are indexes that allowlook ups, therefore giving programmatic access to elements.

When any page renders in a Browser, the time it takes to render isdirectly dependant on the amount of information to be downloaded. Theamount of information required to render a Folder is less than for aPage. When Pages appear in Edit mode, there is yet more informationrequired to render it. Therefore, the quickest load time for aQuickPlace by first using a folder 176 as the first page the user seeswhen upon selecting a place. Once users have visited a folder 176, asubset of the resources used to render a page 182 will already have beendownloaded. The folders used by developers are slightly different tothan the folders users would use. The h_Index lists the published pagesin the Place and appears as the standard index of a Place, and the h_TOCis the table of contents list.

Some of the folders in look ups by developers are set forth in Table 5.

TABLE 5 VIEWS USED TO REFERENCE OBJECTS View Name Description h_IndexProvides a list of all published Pages in a Room, listed by h_UNID, theunique identifier for a Page. Lists all published items in a Room, thisnot only includes Pages but all of the Objects in a Place. For example,Pages, PlaceBots, Fields, Skins and Forms. h_QDK Every Design Note in aPlace. The h_QDK view contains a form formula to open differentdocuments using different forms. For example: If the field “h_Type” is“0” then use the form named “h_Page”. The result of this form formula isthat the QDK view allows developers to inspect the properties of someDesign Notes. The supported types are: “h_Page”, “h_Folder”, “h_Room”,“h_SubRoom”, “h_Error” and “h_RoomType”. h_TOC List of all itemsdisplayed in the Table Of Contents. Items must have the “h_IsInTOC”field with a value of “1” and be published with no replication-saveconflict. (All) Every item in the Room. Sorted by the h_Name field: thereadable name of the item. For example “Welcome”, representing thedefault Welcome page.

The Place Object in PlaceBots: Internally, default QuickPlace Foldershave readable titles. For example the response folder discussion” hasthe internal name of “h_Discussion” in the “h_SysName” field. A newresponse list style folder is called “SchwatzRaum” (which means “chatroom” in German). The internal name of the SchwatzRaum Folder is:

-   “h_F49791727035ACD1C12569510063087C” (which means    “h_F49791727035ACD1C12569510063087C” in German). This unique    identifier can be used in PlaceBots to locate the Folder. A lookup    can be done in the “h_Folders” view of a QuickPlace to find the    readable name of the folder. Another solution is to retrieve the    name of the field by accessing the value in the h_SysName field. The    Table of contents and the Index are special user Folders 176. Only    one TOC and one h_Index exists per Room 174 or Subroom 194. They    exist from the moment the Place or Room is instantiate, and change    them.

Folder Fields

The following Fields are used to define data notes that render asFolders. Folders exist in a visible form within a QuickPlace. In otherwords they can be viewed by opening the NSF file in the Notes Client orDomino Designer. In conjunction with this view, a data note exists,providing information about that Domino View or Folder. Table 6 liststhe fields are contained in the data note and provide information aboutthe Domino View or Folder.

TABLE 6 FIELDS USED TO DEFINE FOLDERS Field Name Descriptionh_FolderStyle When creating a new folder, one is given the choice tocreate a new folder based on a number of templates. This field denoteswhich type of folder has been created. “1” = Standard List “3” =Headline “4” = Slide Show “5” = Response List “7” = Ordered Listh_FolderStorage The “internal” name of the folder, in other words, thename by which it is known to the system. The value of this field is usedin documents to tell QuickPlace in which folder it should be used.h_CanAddPages When creating a new folder, the manger is presented withthe options, to the question “Who can add pages to this folder?”. Ifonly managers is chosen the value of “0” is written to this field. Thedefault is “” which means all authors can add pages to this folder.

Form Object

A form object 178 is a document used to create new QuickPlace content.The Domino equivalent is a data note of type “h_Form”. Form object 178is a resource used to create, manage and display content, thereforedefining the schema of the application. Forms contain fields to holddata, therefore creating and displaying content. Forms can also containscripts within them to provide logic within the Page. For example, aform can contain form validation to make sure that a field contains onlynumbers. Forms can also initiate processes outside the page. This isdone by creating a PlaceBot 184 and associating the PlaceBot with a Form178. PlaceBots 184 are not contained by the Form but there is aassociation between them.

Forms are created with the Domino Form “h_PageUI” with the field h_Typeset to “h_Form”. New forms 178 with custom structure and logic can becreated by room managers.

Form Fields

Table 7 sets forth the fields 180 used to define the structure of a form178.

TABLE 7 FIELDS USED TO DEFINE FORMS Field Name Descriptionh_FormDescription The content of this field appears as the descriptionof the form appearing in the “New” page. h_WorkflowType Allows 1-4approvers and some other h_ApprovalCycle options. This is normally setto “h_Standard”. h_EditorInChief Allows 1 approver and fewer options.h_MultipleEditors By setting this field, all members of QP to edit pagescreated with this form. h_Standard None of the above. h_SetPageComponentsView Should = h_FieldDefinitions

Field Object

Field object 180 is used to construct (HTML formatted) input fields informs 178. The Domino equivalent is a Data note of type “h_Field”.Fields are constructed from the Domino Form “h_PageUI” with a the fieldh_Type set to “h_Field”.

QuickPlace field object 180 defines the structure of the container, notthe content. The values contained in a page 182 are contained by thepage, not the fields 180. The h_FieldType attribute to a field 180determines what sort of field it is. This determines what the field willdo when it is rendered in a browser. For example, a field 180 of typeh_DateControl will provide the user with a date picker widget.

Domino fields are used to define the attributes of QuickPlace fields 180are set forth in Table 8. QuickPlace fields 180 are drawn to the screenas HTML, they are not created by a Domino Field in a Domino Form.

TABLE 8 FIELDS USED TO DEFINE FIELDS Field Name Description h_IsUserDefined h_True means this is a custom form h_PublishInFolder UNID of thefolder +“|” + h_FolderStorage name of the folder h_Name “Import” and isrelated to the h_SystemName field which often has a similar value suchas “h_Import”. h_FieldLabel Instructional information that might beuseful for someone editing this field. Similar to the Statich_FieldType. Containing information to help the user, but only displayedin edit mode. “For example: <script> (h_CurrentSkinType == ‘h_Edit’ )?“”: C(self, ‘Note: Clicking on the title of this page in its folder or inthe sidebar will open the page that it points to. To edit the page againlater, click its title in the Index.’);</script>” h_ContainerUNID TheUNID of the Form which contains this field. QuickPlace uses a DesignNote to create forms, each of these having an internal name. Theh_ContainerUNID contains the internal name of one of these QuickPlaceForms. h_FieldType There are many different types of Fields. Thefollowing types are listed as examples to help understand how Fieldswork in general. “h_Attachments”= Enables the attaching of files.“h_CalendarControl”= Includes date and time controls and a durationfield “h_DateControl”= Date field with date picker widget “h_DateTime”=Contains Date and Time information. “h_DocAuthor”= Contains a DominoHeirachical name of the original Author of the Document. “h_DocCreated”=Creation date of the page. “h_DocModified”= Modified date of the page.“h_DocSize”= Size of the page. “h_NamePopup”= Select listing members ofthe QuickPlace “h_RichText”= Rich text field. Allowing editing via therich text editor applet. “h_Serial”= A unique number to identify thedocument. “h_Static”= Static text, used to provide information about theaccompanying field. May also include link to an image. “h_Subject”= TheDocuments subject. “h_TaskControl”= Used in the Task form to insert thetask control tool. “h_TextInput”= Simple text equating to the “<input>”field in HTML. “h_TextPopup”= Text select list, equating to the“<select><option>”in HTML. “h_TimeControl”= Select lists for hours,minutes, AM/PM. “h_CalendarControl”= Field containing control tool usedin the calendar field. “h_CreateMSExcel”= Field enabling the upload ofExcel documents. “h_CreateMSPowerPoint”= Field enabling the upload ofPowerPoint documents. “h_CreateMSWord”= Field enabling the upload ofWord documents. “h_Import”= Field enabling the upload of importeddocuments such as HTML. “h_MultipleImport”= Field enabling the upload ofmultiple documents, such as a series of HTML documents.“h_NotifyIndicator”= Field indicating if members should be notified ofthe creation of content or their inclusion in the Contacts1.nsf.

Page Object

Page object 182 is a basic building block for content. The Dominoequivalent is a data note, form and subform. Pages form the basic unitsof content, relying on the structure of QuickPlace to create, manage andrender them in a Web browser. It differentiates structure and contentcleanly. Notes structural elements such as Forms Views and so on providestructure, whereas Notes Documents provide pure data content. In theDomino environment the division between structure and content becomesblurred. This is because when the data in a document is beingrepresented in a Web browser, it is possible to use the data to formatitself using HTML. The data is able to start defining structure bycreating HTML links, tables, references to images and so on. In theQuickPlace OM, the same is true. Pages can be created in a number ofways. Table 9 sets forth the fields used for defining page objects.

TABLE 9 FIELDS DEFINING PAGE OBJECTS h_NotInSearch Having the value of“1” will exclude the field from being included in a full text search.This allows functional content in fields such as JavaScript or statictext to evade returning a hit during searching. h_Position Indicates thefields position of appearance in a form. Typically numbers such as 100are used. h_FieldFormat “h_FieldFormat” indicates formatting options,“h_All” “h_BannerOptional” “h_BannerRequired” h_BannerRequired Alwaysdisplay subject as a banner at top of page h_BannerOptional Allow userto choose banner or not h_NoBanner Do not display the subject on thepage h_FieldIsRequired 1 = The field is required and the user will beprompted if they do not fill it out.

Page Fields

Page Object in LotusScript and JavaScript: developers wanting tocustomize pages 182 will generally want to manipulate the page's field180 values. Fields existing in a Page are generally rendered to the HTMLdocument in the background as JavaScript variables. They are thenvisibly rendered via document.write( ) functions. If a field exists, itcan be accessed in the browser via a variable with the same name as thefield.

The PageBody Field holds the main content or “body” of the page.

Table 10 sets forth the fields 180 used to define page 182 documents inQuickPlaces.

TABLE 10 FIELDS USED TO DEFINE QUICKPLACE PAGES Field Name Descriptionh_Form The QuickPlace form used to create this page. This is not theDomino “Form” field which denotes which form Domino links the file to.The Domino “Form” field will contain “h_PageUI” for virtually allobjects in a QuickPlace. h_PageType This field is set to null when thedocument is a visible document. Only when the object is in design modedo the other values appear: “h_Response” the document is a response to atopic document. This value is only valid in response folders.“h_Revision” this means that the document is being revised, and is notavailable for public access. “h_Mail” means that the document is a maildocument, being either sent or received by QuickPlace. h_Originator Thecreator of this page. This field contains a full hierarchical name, forexample: “CN=David Wyss/OU= QuickPlaceName/OU= QP/O= ServerName”. Allusers have the second OU part of the name set to QP. This is done sothat when QuickPlace is used on an Overlay server (QuickPlace and Dominotogether) QuickPlace can avoid conflicts between Domino registered usersand QuickPlace users. h_NameIsBanner Denotes if the page's name shouldbe displayed as a banner. If it is to be displayed as a banner, thisfield contains the value “1”. Setting this field is done when the userclicks on the “Show the title, author and date on page?” checkbox.

The JavaScript “document.write” method is used when using the PageBodyto write out HTML content in a QuickPlace page. This field can beprinted onto the screen via a document.write(PageBody) method called ina QuickPlace document. The following is an example of using thistechnique.

In a Placebot, write the contents of the document into the PageBodyfield. If the PlaceBot has not run, or not run correctly, the PageBodyfield will be empty. If the document is displayed in a form where thePageBody JavaScript variable is not declared, an error will be reported.To avoid an error through an undefined variable, use the “typeof”operator. This test assigns a message string to the sPageBodyMessagevariable and prints that instead of the PageBody. To customize thismessage, the text in quotes on the PageBodyMessage line is changed. Thenthe following is included in the HTML document:

<script language=JavaScript> if ( typeof( PageBody ) == “undefined” ) {var sPageBodyMessage =  ‘Run the Mapperizer PlaceBot             to seea site map here. . .’; document.write( sPageBodyMessage ) } else{document.write( PageBody ) } </script>

Page Object in HTML: some of the most commonly referenced JavaScriptvariables in Pages are set forth in Table 11.

TABLE 11 COMMONLY USED JAVASCRIPT VARIABLES IN PAGES Field Name DataType, Description h_Name String, readable name of the Page PageBodyString, content of the page. h_SystemName String, the internal name of apage. For example, ‘h_Welcome’ h_Originator String, full Notes formatname of the document creator For example: ‘CN=AnnaRath/OU=Millennia/OU=QP/O=Server’; h_IsPublished String, numberrepresenting “1” for published or “0” for not published.h_LastTimePutAway String, representing the date and time the Page waslast saved ‘09/03/2000 07:54:08 PM’ Form String, Domino Form name usedto create the Page. Most documents in a QuickPlace are created with the‘h_PageUI’ Form. The value that differentiates fields is the h_Typefield. HTTP_COOKIE String, all cookies available to that Page. HTTP_HOSTString, name of the server. For example ‘millennia.com’ HTTP_REFERERPage used to send the user to this page. HTTP_USER_AGENT String, browserused to access the current Page. For example: ‘Mozilla/4.0 (compatible;MSIE 5.0; Windows NT; DigExt)’ REMOTE_USER String, full name of theperson reading the Page, for example: ‘CN=DougMudge/OU=Millennia/OU=QP/O=Server’; Server_Name String, the server name,for example: ‘dwyss.lotus.com’ h_DocSize Integer, size of the page, forexample: 4705 h_ModifiedDate String, date and time the page was lastsaved, for example: ‘09/03/2000 07:54:05 PM’;Using Notes name format in pages can be done with the followingJavaScript Function:

function fnGetSimpleName(sTxt) { iTxtStart = sTxt.indexOf(‘=’);iTxtStart++; iTxtEnd = sTxt.indexOf(‘/’); if(iTxtEnd == −1) iTxtEnd =sTxt.length; sTxt = sTxt.substr(iTxtStart,iTxtEnd = iTxtStart); returnsTxt; }; return fnGetSimpleName(‘CN=Doug Mudge/OU= Millennia/OU=QP/O=Server’)This JavaScript will return the string “Doug Mudge”

PlaceBot Object

A PlaceBot object 184 is a Java or LotusScript Domino Agent, used tocreate or manipulate QuickPlace objects automatically. DominoEquivalent: Domino Agent.

For Java and LotusScript programmers, the PlaceBot is the main way ofimplementing sophisticated functionality to a QuickPlace. Within thebounds of an HTML document, industry standard authoring tools such asHTML are used. To make links between Objects and manipulate QuickPlaceObjects, PlaceBots are used.

Theme Object

A theme object 186 is a group of files which defines the look and feelof a QuickPlace. The Domino equivalent is a group of data notes.

Themes are a mechanism for determining the layout and appearance of aQuickPlace. They also help introduce functionality, and although nottheir primary function, some content. There are two types of themes 186in QuickPlace. User defined or custom themes” and default Themes.

Subroom Theme Object

The subroom theme object 188 is a subset of themes 186 in a QuickPlace.The Domino equivalent is a data note. By default, subrooms 194 inheritthe theme 186 being used by the (main) room 174. Only when the themebeing used in the subroom 194 has been modified, does it actindependently of the room 174.

Member Object

A member object 190 is a data note listing a user in the Contacts1.nsf.The Domino equivalent is a note in contacts1.nsf. Members 190 arerecords specifying user-access to a room 174. A member note containsinformation about a team member of a QuickPlace. In addition to thisdata, the member must be listed in the access control list (ACL) ofmain.nsf and in a group in names.nsf to pass authentication.

Table 12 sets forth the fields 180 used to define members 190.

TABLE 12 FIELDS USED TO DEFINE MEMBERS Field Name Description h_PasswordThis member's password. Encrypted with @Password h_FirstName Thismember's first name h_LastName This member's last name h_PhoneNumberThis member's phone number h_EmailAddress This member's email address

Table 13 sets forth the fields 180 used to define Groups.

TABLE 13 FIELDS USED TO DEFINE GROUPS Field Name Description h_MembersThe list of members who belong to this group, listed in full heirachicalformat.

Subroom Member object

A subroom member object 192 is a subset of entries in the main room 174of a QuickPlace. The Domino equivalent is a Data note in contacts1.nsf.Subroom member 192 has a similar structure to a room member 174, butspecifies user-access to the SubRoom. These SubRoom members 192 are asubset of the (main) room 174 members list. This means that to grantaccess to new users, they must first be added as readers (or greater) inthe main room 174.

SubRoom Object

A subroom object 194 is a container within a QuickPlace with separatesecurity to main Room. The Domino equivalent is an NSF Database.Subrooms 194 are similar in structure to Rooms and are used to creatediscreet meeting places for subset of the Members in a Place.

The subroom object in PlaceBots: To locate a room, look in the mainQuickPlace Server directory, then look into the Place Object (adirectory bearing the name of the QuickPlace). The Subroom will be named“PageLibrary” followed by a 16 digit hexadecimal time stamp number suchas “0123456789ABCDEF” then the “.nsf” suffix. By way of example, thefollowing script looks for a Subroom to the Millennia place:

Set dirPlace=New NotesDbDirectory( g_sServerName )

Set ndbPlace=dirPlace.GetFirstDatabase( DATABASE )

sNdbPlaceFilepath=ndbPlace.FilePath

If Instr(1, Lcase( sNdbPlaceFilepath ),

-   -   |QuickPlace\millennia\pagelibrary| )

Then

The Instr method has been used to look for this database, down to thePageLibrary part of the string, because it is difficult to know what the16 digit number will be.

Page Object in HTML: To create URLs to reference Subrooms, the URL isbuilt in the Main Room using either the “h_Area” view or the “h_TOC”view to create the path. This View contains the “h_LocDbName” field asthe first sorted column.

Resources Object

A resources object(not shown) is database of shared resources, having asits Domino equivalent NSF Database. It serves as a centralized containerfor resources required in all QuickPlaces on a server. Images, layoutfiles and fonts are stored in this database. For example resources suchas the button that appears beside the simple search image “Go.gif” isstored in this database. The easiest way to find items in this databaseis by scrolling through the h_SystemNameView. A dummy form may be usedto view such elements.

Common QuickPlace Object Fields

In Tables 14 through 18, fields and JavaScript variables in the h_PageUIform are set forth. These include general fields which can be customizedfor each layout, fields to define publishing status, fields for defininglocations, fields for defining security, fields for defining workflowstatus, fields for defining calendars, respectively.

System objects have special meaning depending on the type of object. Thefollowing tables describe fields in various QuickPlace Object types.

TABLE 15 FIELDS USED TO DEFINE PUBLISHING Field Name Descriptionh_IsPublished 1 = This object is currently published h_IsHidden 1 = Thisobject is not shown to the user h_SetReadScene The name of the defaultscene (subform) to use when viewing this object h_SetEditScene The nameof the default scene (subform) to use when editing this objecth_PublishedVersionUNID If this object is being edited and the currentobject is the draft version, the UNID of the published version of thisobject. h_DraftVersionUNID If this object is being edited and thecurrent object is the published version, the UNID of the draft versionof this object. h_LastTimePutAway The last time that this object waschanged: Published or Saved under construction.

TABLE 16 FIELDS USED TO DEFINE FOLDERS LOCATION Field Name Descriptionh_FolderUNID The name or UNID of the Notes Folder where this pageresides. h_IsInToc 1 = This object is shown in the Table of Contents(sidebar). h_CurrentPosition The position of this object with respect toother objects in the collection. h_SetParentUNID If this is a child orresponse object, the UNID of the parent object.

TABLE 17 FIELDS USED TO DEFINE SECURITY Field Name Description h_ReadersIf this object is protected from readership, the list of names, groups,and or roles that can read this object. h_Authors If this object isprotected from authorship, the list of names, groups, and or roles thatcan author this object.

TABLE 18 FIELDS USED TO DEFINE WORKFLOW Field Name Descriptionh_WorkflowStage Indicates the status of the document within theworkflow. h_New = Created but not yet submitted for approval h_Submitted= Has been submitted and it is being reviewed h_Published = Has beenapproved h_Rejected = Has been rejected h_SetNextStageUser The name ofthe next person in the workflow cycle. h_CurrentApprover A numberdesignating the current person in the workflow cycle. 0 means theOriginator. The list of persons associated with the workflow cycle isstored in the form used to create this page.

Customizing the Object Model

While much of a QuickPlace can be customized via a browser, there aresome parts of QuickPlace which can only be customized using a NotesClient and or the Domino Designer.

Changes that can be made via a browser, using Web authoring tools suchas an HTML editor relate more to the user interface. For example,editing a skin can be done using an HTML editor. Changes made toQuickPlace Objects are done through the Notes client and in DominoDesigner. For example, inspecting and customizing the images appearingin default QuickPlace pages must be done via the Notes Client.

In order to implement PlaceBots (Bots) in a QuickPlace it is cumbersometo test the Bots only in QuickPlace, especially when uploading thePlaceBots each time over the Internet. The Notes Client and DominoDesigner may be used as a local test environment, thus allowing changeson the Bots, as well as providing an integrated development environment,with help files and debugging mechanisms. When finished creating andtesting the Bot in the Designer, it may be uploaded to the QuickPlaceand testing finished there. Using the Notes Client and the DominoDesigner also allows creation of new objects in a QuickPlace. Takingthis a step further, it is possible to redefine the object model, byadding features to a standard QuickPlace. Core Domino technology is aproven platform, providing many powerful tools for a project. Fordevelopers who are not familiar with Domino, they can use a wide rangeof development skills such as HTML, XML, DHTML, JavaScript, Imagemanipulation, Java and C++. Domino developers can also leverage Dominodevelopment skills, but either way it is possible to create robustweb-based applications, without having to re-invent the wheel.

QuickPlace Object Model and HTML: Building URLs

Building URLs in a QuickPlace is an important issue, due to the factthat QuickPlace is a browser based application. Understanding QuickPlaceURLs is also a good way of understanding the object hierarchy inQuickPlace. The relationship between URLs and the QuickPlace Objectmodel flows in both directions. Understanding the structure of URLshelps understanding the QuickPlace Object model. Conversely, once theQuickPlace object model is understood, how to use URLs to manipulate aQuickPlace becomes apparent.

URLs in QuickPlace use the same structure as in Domino. Domino URLsallow locating documents by using the key value of the first sortedcolumn of a view, then generate a URL to link to a document using thiskey. Once the documents are located, they are not always opened in thebrowser. Sometimes they are read and their contents exposed and used byother objects.

An example of locating a file without opening it is when a QuickPlaceskin accesses a JavaScript LSS file. The user never sees the LSS page,but its contents are used by the visible page to render objects andperform functions. To locate a document in Domino, the initial part ofthe URL is pointed to the host server, then the database containing therequired document. The next part of the URL must point to a view withthe first column specified as being sorted. This first, sorted columnbecomes the key column. Then a URL is used to open the document, as inthe following example:

http://Host/Database/View/Key?DominoURLCommand

Where:

-   -   View: is the name of the view. To access a document regardless        of the view, substitute a zero (0) for the view name and specify        the document by its universal ID.    -   Key: is the string, or key, that appears in the first sorted or        categorized column of the view. If the key has spaces in it,        substitute these for plus signs when creating a URL.        This syntax is used to open, edit, or delete documents and to        open attached files. Domino returns the first document in the        view whose column key exactly matches the Key. There may be more        than one matching document; Domino always returns the first        match. The key must match completely for Domino to return the        document. However, the match is not case-sensitive or        accent-sensitive.    -   DominoURLCommand: Is the instruction to Domino of what to do        with the file when found. For example, ?OpenDocument,        ?EditDocument and ?DeleteDocument.        If this DominoURLCommand is omitted a default will be        substituted. For example, in the previous URL if the        OpenDocument argument is omitted in a URL command the document        will still open because the command is automatically interpreted        as OpenDocument.

The structure of URLs in a QuickPlace is the same as in any Dominodatabase. QuickPlace objects are quite often referred to via relativeURLs. For example, to reference a page that has been created, thefollowing syntax is used:

-   ../../h_View/PageName?OpenDocument    Where: “../../” section at the front of the URL creates a relative    URL, is interpreted by the Domino server as referring to the parent    objects of the current object (h_View and PageName).

EXAMPLE

-   -   http://www.mercury.com/register.nsf/Registered+Users/Ja        y+Street?OpenDocument    -   http://www.mercury.com/register.nsf/0/466c5172561e1c5c852566c2005f6bbb?OpenDocument

Many QuickPlace objects in QuickPlace have internal names beginning with“h_”. This is refers to the internal name of QuickPlace which is“Haiku”. To reference images, JavaScript library files or files otherthan pages, the following syntax can be used . . .

-   -   ../../h_Index/Document+Name/$File/Imagename.gif?OpenElement        Or . . .    -   ../../h_Index/Document+Name/$File/ScriptLibName.js?Open Element        Many objects in QuickPlace can be located via the h_Index View.        It contains links to many of the published objects in a        QuickPlace. When referencing a JavaScript file the ?OpenElement        argument is used. This is to tell Domino that the file being        accessed is not a page to open, which is the default action.

Building URLs: Referencing Images

The following section deals with the issue of using images inQuickPlace. Referring to FIG. 6, due to the fact that QuickPlace is aplatform for creating Websites, images 242, 252 form a vital part of theQuickPlace object model. QuickPlace's structure provides many ways toinclude images in pages. For example when creating skin files 260, theimages 242 are automatically uploaded into the QuickPlace 172 when theskin file 230 is uploaded.

Described hereafter are techniques involved for fully automatedimporting procedures within QuickPlace. An example of an automatedimporting would be when creating and uploading a Microsoft Word file250. When this is done the images are imported without anyinterventions.

There are also instances where some developer intervention is required,such as when creating a Skin file 230, or writing an importable HTMLfile 254, or referencing files required to display the results of aPlaceBot and so on.

Creating skin files are fully described hereafter in connection withthemes.

Three methods are used for importing images. These are:

Method 1: Provide a URL to an image and let QuickPlace upload the image.This method is used when creating skins and imported HTML documents thatdo not use JavaScript to reference images.

Method 2: Create a URL, have QuickPlace upload it, then reference itusing HTML or JavaScript. This method is used when rendering image usingJavaScript.

Method 3: Manually upload images into a document and reference them viaURLs from a separate document. This method is used if the image is verylarge and it desired to have the user's browsers be able to cache theimage; or if the image is referenced within a JavaScript function(QuickPlace does not import images when they appear within JavaScripts);or the image is referenced within a PlaceBot which creates new pages.

The solutions selected for a particular application may be a mixture ofall three. For example:

Referencing Images: Method 1. Create a Skin file or HTML imported pageand let QuickPlace import it. This works in skins and imported HTML, andis the easiest way of importing images into Skins and HTML Pages. When avalid link to an image within an HTML page or a Skin is created,QuickPlace will upload it automatically when the Skin or HTML file isuploaded. For this to work, a valid URL must be created. This may bedone as follows:

-   -   In the skin file or importable HTML document, download all the        images in a local directory. The simplest way to do this is to        save them in the same folder as the skin or HTML page. For        example, the URL for an HTML file may be:    -   <img src=“transparent.gif” width=5 height=1 alt=“”border=“0”>

Referencing Images: Method 2. Prompt QuickPlace to import the file intothe current document, then reference the file using JavaScript. Thismethod is the most efficient method to use when referencing an image viaa JavaScript function (in a Skin for example) or when updating adocument via a PlaceBot.

To force QuickPlace to upload the image, a valid URL to the image at thetop of the page must be created. By rendering it in a 1 pixel×1 pixelsize, making it too small to see, the image is still uploaded, but theuser will not notice the image. The images must also be named when theyappear in their 1×1 pixel format. By using this name, the image is madeavailable to JavaScripts below it on the page. This is done by addingthe image to the source code near the top of the page. To forceQuickPlace to upload the image, it is rendered in HTML format, then theuploaded image referenced in the JavaScript.

Overview: PlaceBots

In accordance with a preferred embodiment of the invention, PlaceBotsare provided for sharing documents and holding discussions with teammembers, for adding program logic to a place itself to perform actionswhich can be triggered as the result of submitting a form or scheduledto run at a particular time. For example, every three hours a PlaceBotprogram may execute to browse customer complaints, parse for specifickey words, and move documents to related specific folders. Or, aPlaceBot may be written to perform actions responsive to customercomplaint.

A PlaceBot is implemented by an agent. For example, a browser usercreates a reviewer, sends the invitation, adds logic—using Java code.Then, the Java code is attached to a QuickPlace by dragging and droppingthe code into a QP form. The QP server receives and compiles the codeinto a notes agent. Thus, code is integrated into a QuickPlace using abrowser. The QuickPlace server compiles and link edits the code so thatevery time a reviewer is created that code gets run.

Overview: Imported HTML Forms

In accordance with a further embodiment of the invention, a review formmay be designed in HTML separate from QuickPlace. The resulting form isthen dragged and dropped into QuickPlace, which creates a form for it.This is done by creating a field for each html tag. Thus, each HTMLfield is parsed to create a corresponding QuickPlace field.

For HTML files, the HTML file is parsed, the linked images found, andthe URLs processed. The original file, linked files, and the resultingHTML are then saved on the page with the HTML displayed in read mode,and the orginal file in edit mode.

Overview: MicroSoft Office Based Forms

In accordance with a further embodiment of the invention, an existingExcel spreadsheet or Word document in a power point presentation, forexample, is used as a template, dragged and dropped by the browser userinto a QuickPlace, which then creates from it a QuickPlace form.Thereafter, users can create new MicroSoft documents using theQuickPlace form.

For Office documents, the MicroSoft office native mechanism is used toconvert the page to HTML. The original file and the resulting HTML arethen saved on the converted page, with the HTML displayed in read mode,and the original file in edit mode.

Overview: Forms and Task Fields

In accordance with a further embodiment of the invention, a web browserway of creating and designing forms is provided. A browser user may,using QuickPlace and interacting with the QuickPlace user interface,create a form as an object of the QuickPlace and select and createfields for that form.

Overview: In Place Editing

In accordance with a further embodiment of the invention, a browser usercan create MicroSoft Office documents from within QuickPlace, such as anew Excel web sheet. QuickPlace will automatically launch Excel, andwhen Excel is closed, QuickPlace will bring in the Excel spread sheet.

Using HTML

Because the Page, ListFolder, and Slideshow layouts share so many commoncomponents, one HTML file that applies styles to these three layouts canbe created. HTML for the Slideshow Folder is created, which contains thesuperset of components used in the three layouts. To control how thenon-applicable components display for a layout—for example, the Jumpcomponent for the Page layout, and the AuthorAndModified and Revisioncomponents for the ListFolder—various results are achieved by settingthe emptyFormat, prefixHTML, and postfixHTML parameters.

For example, to have the empty components occupy the same vertical spaceas they do when in use, set the parameter as follows:

emptyFormat=“&nbsp;”

By placing each component in a separate table row, the component's row“collapse” when it is empty, so that it occupies no space. Given thatthe prefixHTML and postfixHTML parameters are not output when thecomponent is empty, these parameters can be used to provide thefollowing table structure:

emptyFormat=“”

prefixHTML=“&lttr>&lttd>”

postfixHTML=“</td></tr>”

Style Sheet Selectors in QuickPlace

Referring to FIG. 7, a typical QuickPlace user interface 370 includes asidebar (TOC) 372, page title 374, author and modified field 376,actions bar 378, logo 380, path 382, page content 400, and actionsbuttons, such as quick search 384, advanced search 386, whatsnew 388,chat 390, notify 392, print 394, tutorial 396 and help 398. Each ofthese is customized by using tags or selectors which deal with borders,background, text, and so forth, in accordance with a style sheet.

A standard default stylesheet is always output with any theme, so thatone need only to specify the selectors that are to be changed. Undefinedproperties will fall back to those defined in the default stylesheet.

Tables 19 through 27 describe Style Sheet (CSS) Selectors.

TABLE 19 Tag Styles CSS Selector Description and Notes body, td Defaulttext style. Note: specify both tags to set the default text style. aAnchor style. Note: see also several other more specific anchor styles,below. a:hover Default style of anchors when mouse is over the anchor.Note: IE only. form Default style of forms. Note: The margin-bottomproperty is set to 0px by default to remove unwanted whitespace from thebottom of all forms. (Note: Other tags, such as h1, h2, etc., can alsobe styled as needed.)

TABLE 20 Page Background CSS Selector Description and Notes .h-page-bgPage background. Note: class assigned to body tag of all pages. For IEonly, the margin properties can be set to control the page margin.

TABLE 21 Folders, What's New, Search Results, Tasks (list view) CSSSelector Description and Notes .h-folderBanner-bg Background of folderbanner. Note 1. .h-folderBanner-text Text in folder banner. Note 1.a.h-folderBanner-text Anchors in folder banner. Note 1..h-folderBannerSelected-text Text of selected (“current”) item in folderbanner. Note 1. a.h-folderBannerSelected-text Selected anchor in folderbanner. Note 1. .h-folderItem-bg Background of items listed in folder.Note 1. .h-folderItem-text Text of items listed in folder. Note 1.a.h-folderItem-text Anchor listed in folder. Note 1..h-folderCompact-text Compact text of item listed in folder. Note 1..h-folderAbstract-text Abstract text of item listed in folder..h-folderBar-bg Background of bar to left of a thread. .h-folder-dl {Indentation of responses in response folder. Note: by default, themargin-bottom property is set to 0px to remove unwanted whitespace belowindented items in response folders. .h-folderInterspace-bg { }Background color of vertical space between responses..h-folderInterspace-text { Height of vertical space between responses.Note: use font-size to set the height. .h-folderSpace-text { Height ofvertical space between threads. Note: use font-size to set the height.Note 1: This style is used for the banner that displays column titles,as well as other banners in What's New, Search Results, etc.

TABLE 22 Tasks (timeline view) CSS Selector Description and Notes.h-tasksBannerNow-textbg Highlighted current date in Tasks banner..h-tasksItem-bg Background of items listed in Tasks..h-tasksItemTimeline-bg Highlighted period of a task..h-tasksItemMilestone-bg Highlighted period of a milestone

TABLE 23 Calendar CSS Selector Description and Notes.h-calendarLabel-text Date label. .h-calendarLabelSelected-text Datelabel (today's date). .h-calendarItemOther-bg Background of day not incurrent month. .h-calendarItemToday-bg Background of today's date.

TABLE 24 Text and fields in Page layout CSS Selector Description andNotes .h-field-text, Style of the text value of a field. .h-field-texttd Note: use this exact selector, as shown, to style field textdistinctly from regular page content. .h-pageSmall-text “Smallprint”page text. .h-fieldSmall-text “Smallprint” text content of fields..h-fieldHeader-bgtext Field header. .h-fieldOrder-bgtext Number to theleft of the field header. .h-page-text Anchors inside the pageContentskin a:visited component which have been visited. Note: IE only.

TABLE 25 Edit Layout CSS Selector Description and Notes.h-fieldHeaderEdit-bgtext Field header .h-fieldEdit-text, Fielddescription text. Note: .h-fieldEdit-text td use exact selector, asshown. .h-fieldOrderEdit-bgtext, div Number to the left of the.h-fieldOrderEdit-bgtext td field header. Note: use exact selector, asshown. All properties in this selector must be marked ! important totake effect. E.g., color: green! important. .h-fieldSmallEdit-text Smallfield text. Note: all properties in this selector must be marked !important to take effect. .h-fieldSpecialEdit-text Special field text.Note: used in Task Info field. All properties in this selector must bemarked! important to take effect.

TABLE 26 QuickSearch CSS Selector Description and Notes.h-searchField-text Style of the text field associated with thequickSearch skin component.

TABLE 27 Classes defined by the default theme The classes listed beloware not built in to QuickPlace, but are defined by the default theme'sstyle sheet. (Custom themes are not required to use these classes, andare free to define any other classes as appropriate.) However ifmodifying the default theme, these classes can be modified to get aparticular effect. CSS Selector Description and Notes .h-logo-text Logotext. .h-heading-textbg Heading about table of contents and tools boxes..h-sidebar-bg Background of table of contents and tool boxes..h-toc-text Text of item listed in table of contents..h-tocSelected-text Text of selected item listed in table of contents..h-nav-text Navigation link. .h-tool-text Tool link. .h-signIn-text SignIn link. .h-actionButtonBorder-bg Border of action button..h-actionButton-bg Background of action button. .h-actionButton-textText of action button. .h-actionSpace-text Space between action buttons..h-pageTitle-textbg Page title. .h-pageAuthorMod-text AuthorAndModifiedtext. .h-revision-text Revision link (draft | published)..h-revisionSelected-text Selected revision link .h-accent-bg Accentcolor. E.g., used in rule at bottom of page. .h-headlineFolderTab-bgBackground of unselected tab in headline folder..h-headlineFolderTab-text Text of unselected tab in headline folder..h-headlineFolderTabSelected-bg Background of selected tab in headlinefolder. .h-headlineFolderTabSelected-text Text of selected tab inheadline folder. .h-edit-bg Background of edit layout “docket”..h-actionButtonEdit-text Text of action button in edit layout..h-actionButtonBorderEdit-bg Border of action button in edit layout..h-actionButtonEdit-bg Background of action button in edit layout..h-shadow-bg Shadow. Note: used in sidebar and in edit layout “docket”shape. .h-shadowCorner-bg “Missing” corner of shadow area.

PlaceBots

A PlaceBot is a Domino agent, written either in Java or LotusScript,that automates a task. Using a PlaceBot (or “Bot”), one can access,process, and manage the data in a QuickPlace. For example, one might usea PlaceBot to send E-mail to members of a QuickPlace that notifies themwhen a document of interest is edited. One can create a PlaceBot thatruns when a form is submitted or on a scheduled basis. A PlaceBot mayalso be run manually. A PlaceBots is created using LotusScript or Javato manipulate the Domino back-end object classes. For completedocumentation on the Domino Object Model and how to work with objectsusing LotusScript or Java, see the Lotus Domino R5 Programming Guide.

It is possible to write, debug, and compile Java code for a PlaceBot ina Java development tool, such as Symantec Visual Cafe. One can thenimport the .java file, or compile and import a .class or .jar file. Itis also possible to write Java or LotusScript code in any editor andimport the resulting files into the QuickPlace. When Java PlaceBots areuploaded, they are automatically compiled, and a syntax check is done onthem.

Triggering PlaceBots

QuickPlace has a page in the Customize area where settings to controlhow and when the PlaceBot runs are specified. These settings are similarto the Domino Agent settings, but not the same.

There are two ways of triggering PlaceBots. Scheduled PlaceBots,triggered by a timer event or Form PlaceBots which are triggered by thecreation of documents, based on the form type.

Scheduled PlaceBots

Scheduled PlaceBots are processed by the agent manager, and have theAccess rights of the QuickPlace Manager.

Form PlaceBots

Form PlaceBots are triggered by the creation of a document based on anyof the user forms in a QuickPlace. For example, if a new HTML form iscreated, one can specify that the Bot is to run on documents createdwith that form. If PlaceBots are triggered by document creation, theyhave the same access rights as the person who created the document.

The Difference Between PlaceBots and Domino Agents

PlaceBots are in effect, Domino agents. However, a PlaceBot is installedinto a QuickPlace via the QuickPlace upload control. An agent isinstalled using the Domino Designer. Also, a PlaceBot can be created inany text editor, then uploaded. Another advantage of PlaceBots overAgents is that they can be stored as small LSS, Java JAR or Class fileson a hard disk, and installed quickly on any QuickPlace, even withoutadministrative access to the server. Manager access to the QuickPlace isall that is required.

PlaceBot Security

When PlaceBots are run on a scheduled basis, they inherit the accesscontrol of the server. When PlaceBots are run manually, they have theaccess rights of the person triggering them. In other words, one musthave Manager access to create, edit, copy, delete, or run PlaceBotsmanually.

Write a PlaceBot

In the following example of how to write PlaceBots, a dummy QuickPlaceis created using the Domino Designer, as follows:

-   1. Create a QuickPlace.-   2. Create documents, folders, links, and so on that the Bot will be    referencing.-   3. Close down the QuickPlace server.-   4. Create a copy of the NSF file(s) that were created by QuickPlace.    In most cases this will be the “main.nsf”.-   5. Open the NSF file in Domino Designer and start writing a Domino    Agent.-   6. Test the PlaceBot in the NSF.-   7. Export the Agent and save java agents as a .Java , .JAR , .Class    or .ZIP file. If writing a LotusScript file save it in .LSS format.    To export a Java file, press the Export button in the Designers    pane. To export a LotusScript file, right click on the designers    pane and select Export.-   8. Make sure the QuickPlace server is started and return to the    original QuickPlace.-   9. Go into Customize ->PlaceBots then create and test your PlaceBot.-   10. For small changes it is easier to open the LSS file in a text    editor, then copy the changes back into the original LotusScript    Agent. For the more complex changes go back into the Domino    Designer.    Java PlaceBots

Java PlaceBots accept file types .JAVA .CLASS and .JAR. It is possibleto also upload multiple files. PlaceBots can be writen in a text editor,using QuickPlace as the test environment. It is possible also to usethird party Java development tools, such as Visual Age for Java.

LotusScript PlaceBots

Creating PlaceBots using LotusScript is essentially the same as writingan agent for a Domino application. There are two alternatives forwriting LotusScript (LSS) PlaceBots. It is possible to write LSS Bots ina text editor and test the Bots in the QuickPlace. This section usessome examples of LotusScript that show the process of creating aPlaceBot and exposes the object model.

An exemplary PlaceBot has the following list of functional features:

-   -   Graphical display of folder/page relationships    -   Alphabetical list of pages    -   Theme like customizing of the map page        -   Easily modify the folder and page images        -   Full control over fonts, sizes, colors and so on        -   Ability to wrap the document in any HTML required    -   Selective page mapping—Pages and Links but not Room links    -   Map document could be switched off if decided by the Manager    -   Map document could appear wherever the Manager decided    -   The map document would be updated whenever a new Page document        was added.        PlaceBot Description

Referring to FIG. 9 in connection with Tables 2201-2225, an exemplarymethod for creating a PlaceBot will be described.

In step 402, variables relating to the session, the database and itsmajor structures such as view and key documents are declared.

PlaceBot starts off by Dimming (declaring) the variables related to thesession, the database and its major structures such as Views and keydocuments. The Dims are typically divided into two groups; dims forNotes related objects, then the writing Dims, which are used in contentcreation, mostly via strings.

In step 404, documents related variables are set, for example using askin for the site map page.

This step, code for which is set forth in Table 28, sets the documentrelated variables. These Sets are related to finding documents, workingfrom the Database, down to the individual SiteMap document. If theSiteMap page is not found in the QuickPlace then the Bot quits. This isto allow a bit of flexibility in the order in which the Bot isinstalled. Errors are not generated done out of order, delete the sitemap page or name the site map page wrongly. This approach also allowsuse of a skin for the Site Map page. The skin file is the SiteMap.htm.This HTML wraps the map, can be modified, place by place, without havingto change the Bot. In its current form, the SiteMap Bot and Pageseparate LotusScript and HTML scripting making the overall programmingof the Bot simpler.

TABLE 28 SET DOCUMENT RELATED VARIABLES CODE sMapDocName = “SiteMap” Setndb = ses.CurrentDatabase Set viewCurrent = ndb.getView( “h_Index” ) SetdocReport = viewCurrent.GetDocumentByKey( sMapDocName ) If docReport IsNothing Then Call logAgent.LogAction(“Mapperizer: Document ” &sMapDocName & “ not found” ) Exit Sub End If

In step 406, the table of contents (TOC) is found and set as a specialview.

TABLE 29 SET TOC AS SPECIAL VIEW Set viewTOC = ndb.getView(“h_Toc”)

In step 408, URLs referencing current QP documents and attached imagesare created.

The looping functions of Table 35 gets each element in the viewTOC thenperforms a number of calculations on that TOC element. Some TOC elementsmay be views, in which case that “sub view” is stored in the variablenamed viewCurrent. To start creating the URL strings for each entry, thefollowing dims and sets are made. The sDbPath now is a string formattedfor use within a URL, in other words its backslashes are replaced byforward slashes. Ascii character 47 is a forward slash, and character 92is a backslash.

TABLE 30 CREATE URLS / ATTACHED IMAGES Dim sFSlash As String Dim sBSlashAs String Dim sDbLabel As String Dim iSlashPos As Integer sDbPath =ndb.FilePath & “/” sFSlash$ = Chr(47) sBSlash$ = Chr(92) iSlashPos =Instr(1, sDbPath$, sBSlash$) While iSlashPos <> 0 Mid$(sDbPath$,iSlashPos, 1) = sFSlash$ iSlashPos = Instr(1, sDbPath$, sBSlash$) Wend

To introduce images onto the current page, a URL is created thatreferences the current QuickPlace document, then the images that areattached to it. These images are automatically uploaded when theSiteMap.htm file is uploaded. The URL uses a lookup in the h_Index inthe current QuickPlace, and references the name of this page, set in thevariable in sMapDocName. The h_Index is a view that allows one to lookup all documents in the QuickPlace using their ID. For example, to getan image:

-   <img src=“http://quickP.com/quickplace/MyPlace/Main.nsf/    PageMap/$FILE/Page.gif?OpenElement”>    To simplify this, the same path structure is kept but made relative:-   <img src=“../../PageMap/$FILE/Page.gif?OpenElement”>

In the script of Table 31, the name of the PageMap document is replacedby a variable. This is to make it easier to change the name of the file.The names of the GIF images names are hard coded. If the developer wantsto modify the SiteMap look, it is easier to just create a new image andsave it with the same name.

TABLE 31 TAG MAP HTML ‘writing sets sFolderImg = |<imgsrc=../../h_index/| & sMapDocName & |/$FILE/Folder.gif?OpenELementborder=0 width=20 height=13>| sPageImg = |<img src=../../h_index/| &sMapDocName & |/$FILE/Page.gif?OpenELement border=0 width=13 height=13>|sPageSubImg = |<img src=../../h_index/| & sMapDocName &|/$FILE/PageSub.gif?OpenELement border=0 width=29 height=13>| sIndentImg= |<img src=../../h_index/| & sMapDocName &|/$FILE/Indent.gif?OpenELement border=0 width=13 height=13>|sHeadingStyleTag = “<span class=h-mapHeading-text>” sStyleTag = “<spanclass=h-map-text>” sFolderStyleTag = “<span class=h-mapFolder-text>”sDetailStyleTag = “<span class=h-mapDetail-text>” sEndStyleTag =“</span>” sIndentConcat = “”

The next few lines set up some more HTML. The first of which is a headerline. The HTML <HEAD> tag is written over when a skin is created, and sothe sHTMLHead variable's contents are not used unless writing to thedisk as an HTML File. This is included for debugging purposes only.

In step 410, map HTML is entered and tagged.

Referring to Table 32, the sHTML01 tag is added to the document beforethe map HTML. This is not at the start of the entire document, but atthe start of the Map. To put code into the true start of an HTMLdocument in a QuickPlace, manipulate the Notes objects directly, usingthe Domino Designer. To insert JavaScript or Style tags in a site mapdocument, put them in the sHTML01 string variable. The sHTML02 tag isadded at the end of the map HTML. This HTML is not at the absolute endof the HTML stream for the page, it appears at the end of the mapsection.

Pipe characters are used to define strings because they allows one toput in un-escaped quote characters, but more importantly the stringsappear as they are typed, making it easier to debug.

TABLE 32 TAG START OF MAP sHTMLHead = |<html><head><link rel=stylesheettype=“text/css” href=“Mapperizer.css”></head>| ‘only for debug sHTML01 =|<!-- start -->| ‘put JavaScripts here or the imported document sHTML02= |<!-- end -->| ‘this will be concantenated at the end

In step 412, a loop through the TOC is executed, and visible textcreated.

In Table 33, start looping through the Table of contents. The view“h_Toc” is very important to this Bot, as it is the main guide tolocating relevant folders and documents. It is also possible to use theh_Index to find all documents, and look at their properties. To get alldocuments, the h_Index is a good view to use. If a document cannot befound in the TOC view, the Bot exits as errors will occur if the loopcontinues.

TABLE 33 START LOOP THROUGH TOC sMainText = sHTML01 Set docInTOC =viewTOC.GetFirstDocument If docInTOC Is Nothing Then ‘make sure the TOCis found Call logAgent.LogAction(“Mapperizer: TOC Not Found” ) Exit SubEnd If

Referring to Table 34, visible text is now beginning to be created,first the title of the page, including the Place name. The StyleTag is aCSS span instruction to help with formatting.

TABLE 34 STYLETAG sMainText = sMainText & sHeadingStyleTag & “AllDocuments in the ” sMainText = sMainText & ndb.Title & “ QuickPlace” &sEndStyleTag

Referring to Table 35, a few of the database statistics are added to themain text string.

TABLE 35 DATABASE STATISTICS sMainText = sMainText & “<br>” &sDetailStyleTag & “Current Database Size: ” & Cstr (ndb.Size/1024) & “k”sMainText = sMainText & sDetailStyleTag & “Created: ” &Cstr(ndb.Created) sMainText = sMainText & “Last Modified: ” & Cstr(ndb.LastModified ) & sEndStyleTag & “<br>”

Referring to Table 36, start cycling through the documents in the TOC.The TOC contains a list of links that refer to items the users of theQuickPlace have chosen to display there. For example in a QuickPlacethere may be a Welcome document, a Discussion view, a link, a slidesshow and some other QuickPlace tools such as Customize. Each of theseelements is represented in the TOC by a data note. The only thing thatthe objects here have in common is that they have the field h_IsInTOCcontaining a value of “1” (text), and that it is properly published (isnot in draft mode and does not contain any $Conflict fields or documentsthat are in draft mode). Published items in QuickPlace are distinguishedby the h_Type field. If this field contains a “0” it is a document, “1 ”is a view and so on. In the section below value of “0” is found in thisfield and the item dealt with as a document.

TABLE 36 TOC PROCESSING While Not ( docInTOC Is Nothing ) IfdocInTOC.h_Type (0) = “0” Then ′it is a doc Set docTemp = docInTOC

Referring to Table 37, now that a document is found, the code can startbuilding the text string for that elements listing. It would be a littlestrange if the site map page was visible in the map, so it is skipped inthe looping process. The sMapDocName variable has the document's nameassigned to it.

TABLE 37 ASSIGN DOCUMENT NAME If docTemp.h_Name (0) <> sMapDocName Then

In step 414, URL strings are built for linked documents.

Referring to Table 38, another type of document that is handled a littledifferently is the Link type document. QuickPlace knows a document is aLink if the field h_URLPointer is not empty. So if the h_URLPointerfield has content, the URL string is built using the content of thatfield.

TABLE 38 BUILD URL FROM LINK TYPE DOCUMENT If docTemp.h_URLpointer (0)<> “” Then ′it is a link sMainText = sMainText & “<br>” & “<a href=” &docTemp.h_URLpointer (0) & “>”

Referring to Table 39, otherwise build the URL using the main view ofany Main.nsf database, the h_Index view. The h_Index view is the mostimportant view for creating unique resource locators (URLs). Thefollowing line uses the Universal Identifier of the page beingreferenced. This value can be found in the first, visible, sorted columnin the h_Index view. Here the script continues building the text stringfor that element's listing.

TABLE 39 BUILD URL FROM MAIN VIEW Else sMainText = sMainText & “<br>” &“<a href=. . / . . /h_Index/” & Cstr(docTemp.UniversalID) &“?OpenDocument>” End If sMainText = sMainText & sPageImg & sStyleTag &docTemp.h_Name(0) & sEndStyleTag sMainText = sMainText & sDetailStyleTagsMainText = sMainText & “ (Last Changed: ” & Cstr (docTemp.LastModified)sMainText = sMainText & “ Size: ” If docTemp.Size < 1024 Then sMainText= sMainText & “0” End If sMainText = sMainText & Cstr( docTemp.Size /1024 ) & “k” sMainText = sMainText & “)“ & sEndStyleTag & “</a>”nLinkCount = nLinkCount + 1 ‘end standard formatting End If

In step 416, database elements are linked.

Referring to Table 40, the next Elseif operator executes if a view isfound, here represented as a list of “notes”. Each of these Notescreates a link to a database element; in this case a view. QuickPlace'sdefinition of a View Note is that the h_Type field is 1. Finding theinternal name of the view being referred to is done by finding the valueof the h_SystemName field, and storing it in the sSysName variable. ThesSysName now contains the internal name of the view. This variable helpsto find the current folder or view.

TABLE 40 LINK TO VIEW Elseif docInTOC.h_Type(0) = “1” Then ‘it is afolder/view sSysName = docInTOC.h_SystemName(0) ‘get the internal nameof the view ‘if it is a link to a QuickPlace tool page

In step 418, response folders are mapped.

Referring to Table 41, it is now known that a folder of a type to maphas been found. The iNested variable is set to 1 if it is a responsefolder and some form of indentation is suitable.

TABLE 41 INDENT RESPONSE FOLDER Else iNested = 0 IfdocInTOC.h_FolderStyle(0) = “5” Then ‘it is a response folder iNested =1 End If

Referring to Table 42, the view name is now put into the viewcurrentvariable. The URL to the view used here is not the database/view, butrather

database/h_Index/viewDesignNoteID.

This is another example of how the QuickPlace Object Model works withDesign Notes. Referencing the design note will redirect correctly to theview. This section of the script does exactly that, and writes some moretext to the sMainText variable, which will later be printed out as themap page content.

TABLE 42 REDIRECT TO VIEW UPON REFERENCE TO DESIGN NOTE Set viewCurrent= ndb.getView( sSysName ) sMainText = sMainText & “<br><a href=. . / . ./h_Index/” & Cstr(docInTOC.UniversalID) & “?OpenDocument>” sMainText =sMainText & Chr(13) & Chr(9) & sFolderImg sMainText = sMainText &sFolderStyleTag & docInTOC.h_Name(0) & sEndStyleTag & “</a>”

In step 420, all documents in the view are gathered.

Referring to Table 43, inasmuch as the folder has been found, andwritten to the sMainText variable, it is now time to get all thedocuments in the view. To do this the docTemp variable is used to gatherall documents in the view. The code in this section is similar to thatfor finding documents in the top level of the TOC. However, they haveseveral subtle differences. The main one that the user sees is that theyare indented to one extent or another. Normal documents are indented onespace (13 pixels), but pages in response folders that are responses areindented a further 13 pixels.

TABLE 43 GATHER ALL DOCUMENTS IN VIEW Set docTemp =viewCurrent.GetFirstDocument While Not (docTemp Is Nothing) IfdocTemp.h_Name(0) <> sMapDocName Then sMainText = sMainText & “<br>” IfdocTemp.IsResponse And iNested Then iIndentDistance = 13 sIndentConcat =“<img src=blank.gif width=” & Cstr (iIndentDistance) & “ height=1border=0>” sPrevSetParentUnid = sThisSetParentUnid Else iIndentDistance= 0 sIndentConcat = “” End If sMainText = sMainText & sIndentConcat

Referring to Table 44, link documents are be indented further becausethey are contained within folders, not appearing in the TOC at the toplevel.

TABLE 44 LINK DOCUMENTS INDENTATION If docTemp.h_URLpointer (0) <> “”Then 'it is a link sMainText = sMainText & “<a href=” &docTemp.h_URLpointer (0) & “>” Else sMainText = sMainText & “<a href=../../h_Index/” & Cstr (docTemp.UniversalID) & “?OpenDocument>” End IfsMainText = sMainText & sPageSubImg & sStyleTag & docTemp.h_Name (0) &sEndStyleTag sMainText = sMainText & sDetailStyleTag sMainText =sMainText & “ (Last Changed: ” & Cstr (docTemp.LastModified) sMainText =sMainText & “ Size: ” If docTemp.Size < 1024 Then sMainText = sMainText& “0” End If sMainText = sMainText & Cstr( docTemp.Size / 1024 ) & “k”sMainText = sMainText & “)” & sEndStyleTag & “</a>” Update the counterfor displaying in the log. nLinkCount = nLinkCount + 1 Start the loopagain. End If Set docTemp = viewCurrent.GetNextDocument( docTemp ) WendEnd If

In step 422, valid links are displayed for HTML accumulated for thepage.

Referring to Table 45, with respect to the other document types, eventhough is not relevant in this situation, it provides an easy way toimplement mapping of room links. It would be possible to extend on thisand go into the database for the room referenced here, and show alldocuments in that room. However, that would breach security principals,to allow users to see all room links. If a user did not have access to aroom, the link would prompt a user name and password box to appear, andthey would be stopped. Users would be informed that a room existed, butthey were not able to enter. According to the QuickPlace model, onlyvalid links are displayed. Also, another line is writen to the log, andthe text finished for the page.

TABLE 45 MAP ROOM LINKS Else 'it must be some other sort of link, suchas a room (h_Type = “3”) End If Set docInTOC = viewTOC.GetNextDocument(docInTOC ) Wend Call logAgent.LogAction(“Agent Mapped ” & Cstr(nLinkCount ) & “ documents” ) sMainText = sMainText & “<br>” & sHTML02 &“<br>”

Referring to Table 46, this is the final step; output of the accumulatedHTML for the page. This code was developed in debug mode ( iDebug=1 )and the file written to an HTML file on the server. In a realenvironment, as these functions are disallowed in PlaceBots, securitywas reduced to allow this to work by setting the default access toManager.

TABLE 46 OUTPUT ACCUMULATED HTML If iDebug Then 'debug version writes toa file fileNum% = Freefile ( ) Open “D:\trash\trash.htm” For Output AsfileNum% Print #fileNum%, sHTMLHead ; sMainText Close fileNum% Else'release version writes to a QuickPlace Main.nsf db docReport.PageBody =sMainText Call docReport.Save( True, True ) End If Then finish off withthe exit and error handing methods. Exit Sub lblLogError: CalllogAgent.Logerror (Err, Error$) Resume Next End SubOverview of the SiteMap.htm Page

In this example, the SiteMap.htm page must be manually imported into theQuickPlace and is the target document for the PlaceBot. In other words,the Mapperizer PlaceBot goes looking for this file and refreshes it. Ithas two parts. The wrapping for the actual map is what is contained inthe HTML file. In the middle of the page is an instruction to render themap, then at the end is some more HTML to finish off the page. TheSiteMap PlaceBot and HTML file allow skin like customization. In otherwords its appearance can be dramatically altered to suit the Place. Thisis done by altering the HTML in the SiteMap.htm file, editing the imagesFolder.gif, Page.gif, PageSub.gif and Indent.gif which are referenced inthe SiteMap.htm file.

To rename the SiteMap page a variable in the Mapperizer PlaceBotsMapDocName is edited. When creating a new site map page, that isrenamed with exactly the same name.

SiteMap HTML Page Description

The SiteMap HTML page is imported into QuickPlace and named SiteMap. Itis basically a wrapper for rendering the images on screen and presentinga single JavaScript document.write command. Everything else is eithercosmetic presentation or error checking. Referring to Table 47, theessential lines in this page render the four images on the screen,forcing QuickPlace to upload them:

TABLE 47 FORCE UPLOAD <img src=“Folder.gif”> <img src=“Page.gif”> <imgsrc=“PageSub.gif”> <img src=“Indent.gif”>

Referring to Table 48, the JavaScript command to print the text createdby the Mapperizer PlaceBot onto the screen.

TABLE 48 PRINT TO SCREEN <script language=JavaScript>document.write (PageBody ) </script>

Referring to Table 49, to make the map more presentable, the images arerendered on the screen in a table. Using a table allows creation of alittle vertical space, and also alignomg the images to the right. Thisis done to make the pixel images a little less obvious to the reader.Due to the fact that the table is only one pixel high, it can be filledwith a color to create a really pretty line.

TABLE 49 RENDER IMAGES ON SCREEN IN TABLE <table width=100% border=0width=10 cellpadding=0 cellspacing=0> <tr> <td height=1 align=right><imgsrc=“Folder.gif” width=“1” height=“1”><img src=“Page.gif” width=“1”height=“1”><img src=“PageSub.gif” width=“1” height=“1”><imgsrc=“Indent.gif” width=“1” height=“1”></td> </tr> </table>

Referring to Table 50, next comes the section which draws the body ofthe document onto the page. The first JavaScript Line here makes surethat the PageBody variable has been declared. Content in the PageBodyfield of a Quickplace document is automatically placed into the PageBodyJavaScript variable. If the “typeof” test in the following textdetermines that the bot has not run, a message is printed onto thescreen giving information on how to get started. This is especiallyimportant because it helps avoid a JavaScript error through an undefinedvariable. The variable PageBodyMessage is the text to change to changethe message displayed on screen.

TABLE 50 DRAW DOCUMENT BODY <script language=JavaScript> if ( typeof(PageBody ) == “undefined” ) { var PageBodyMessage = ‘Run the MapperizerPlaceBot to see a site map .’; document.write( PageBodyMessage ) } else{document.write( PageBody ) } </script>

Referring to Table 51, the Log should now show the following text . . .

TABLE 51 LOG TEXT Started running agent ‘Mapperizer′ on 09/05/200009:31:31 PM 09/05/2000 09:31:31 PM: Mapperizer: IBM Redbook Example09/05/2000 09:31:31 PM: Mapperizer: Run agent: Mapperizer 09/05/200009:31:32 PM: Agent Mapped 18 documents Ran LotusScript code Done runningagent ‘Mapperizer′ on 09/05/2000 09:31:32 PM

Desktop Integration

Although Lotus QuickPlace is a web application that is displayed in abrowser, much of the value that QuickPlace offers the user is itsability to easily allow content creation and content editing using toolsand applications already familiar to the user. For example, inQuickPlace Release 1, users could write documents using Microsoft Word,the most popular and widely used word processor for the Windowsplatform, and then import these documents into QuickPlace. Therefore,Microsoft Word became a content-creation tool for QuickPlace.

In-Place Editing

Referring to FIG. 13, in accordance with a further embodiment of theinvention, a browser user can create MicroSoft Office documents fromwithin QuickPlace 352, such as a new Excel web sheet 354. As isrepresented by open line 357, QuickPlace will automatically launch Excel358, and when Excel 358 is closed, as is represented close line 359,QuickPlace 352 will bring in the Excel spread sheet 356.

Referring to FIG. 6, in general, standard web files 242, 244, 248, 252,254 and 250 are brought into the browser as files 230, 234 and 238 suchas via upload control 240, sent to the web server 258, Domino server 104and QuickPlace extensions 108 and converted into application enabledobjects 260, 262, 264 in QuickPlace 172.

In accordance with a preferred embodiment of the invention, QuickPlaceextends this concept further using better integration with the Windowsdesktop. In particular, the “Desktop Integration” feature area includes:

-   1. Round-trip editing of Microsoft Office and Lotus SmartSuite    documents.-   2. Support for importing additional file formats using the HTML    export engine from Verity.

Round-Trip Editing of Microsoft Office and Lotus SmartSuite Documents

Users are able to create documents based on Microsoft Office and LotusSmartSuite documents, and publish them into their QuickPlace. This isdone by creating a document using Office or SmartSuite independent ofQuickPlace and then dragging and dropping this file into QuickPlace—thisprocess is referred to as “importing” Office and SmartSuite documents.Alternatively, the user will be able to create a page in QuickPlace andspecify immediately that the page's content will consist of an Office orSmartSuite document. The user will then use the selected application toedit the page. This process is referred to as creating a “Microsoft Wordpage,” for example.

In either case, users are able to edit QuickPlace pages using the sameOffice or SmartSuite application that created them. This, in effect,turns Office and SmartSuite into content creation tools for QuickPlace.At the same time, QuickPlace becomes a web publishing tool for MicrosoftOffice and Lotus SmartSuite users. Users will not have to learn a newcontent creation and editing user interface; they will simply use thetools that they have already become familiar with and which they havealready used to create large amounts of content in the past.

Support for Importing Additional File Formats Using the HTML ExportEngine from Verity

Since users may want to import content or information that wasn'tcreated with either Office or SmartSuite, in accordance with a preferredembodiment of the invention, various other file formats are supportedmaking it much more likely that every user will be able to quicklypublish data in collaboration space.

Further in accordance with this aspect of the invention, the importfeature provides that the import code will be run on the server side.Thus, Internet Explorer users' Office and SmartSuite files are convertedto HTML on the client machine using OLE automation. All Netscape users'files—and non-Office/SmartSuite files for IE users—are then uploaded tothe server in native format, and converted to HTML using the “HTMLExport” engine from Verity. Since this conversion will be performed onthe server, no client code must be downloaded for Netscape users.

Round-Trip Editing of Microsoft Office and Lotus SmartSuite Documents

In accordance with a preferred embodiment of the invention,collaboration space users will use OLE automation to support creatingand editing of pages using Microsoft Office and Lotus SmartSuiteapplications. As described below, both Netscape and IE users will havethe ability to import local files into QuickPlace using the HTML Exportengine from Verity running on the server.

For IE/Windows users, the benefits of using OLE Automation are asfollows:

-   1. Each application will be able to provide the best possible    representation of its application data in HTML. For example, the    best way to render a Microsoft Word file in HTML is to ask the Word    application to convert it.-   2. By using OLE automation, QuickPlace will be able to effectively    choreograph the application in question as an integrated editing    tool. When the user creates or edits a QuickPlace document based on    Excel, for example, Excel will appear automatically, allowing the    user to edit the QuickPlace document using Excel.

The primary disadvantage of using OLE automation for creating andediting document is that the target application must be installed on theuser's client machine. To be able to edit a QuickPlace document usingWord, the user must obviously have it installed locally. On the otherhand, importing files using server-side technology will work regardlessof what software is installed on the user's machine.

In accordance with a preferred embodiment of the invention, round-tripediting provides the following features. Each of these will be furtherdescribed hereafter with reference to the various scenarios specified.

-   1. Creation of QuickPlace pages based on an office or SmartSuite    document. (Scenario #1.)-   2. Import existing office and SmartSuite documents into QuickPlace.    (Scenario #2.)-   3. Edit existing QuickPlace pages that were originally created or    imported from an Office or SmartSuite application. (Scenario #3.)-   4. Be able to edit Office 2000 documents saved as a “Web Page” in    their original form. (Scenario #4.)-   5. Export HTML documents from QuickPlace back to the user's hard    drive in their original form. (Scenario #5.)-   6. A new type of QuickPlace form based on an existing Office or    SmartSuite document. (Scenario #6.)-   7. Allow non-empty file attachment fields to be used in forms.    (Scenario #7.)

Scenario 1: Creating a New Page Based on Microsoft Word 2000.

-   1. Referring to FIG. 10 and Figure, a user clicks the “New . . . ”    button in the QuickPlace action bar 378 (FIG. 7). The “New . . . ”    scene 408 appears with a list 412 of available page types. In    addition to the old choices (Page, Imported Page, Calendar Page,    etc.) each Office or SmartSuite application installed on the user's    local machine will be listed with a radio button. The user will know    right away which applications can be used for editing—and won't be    mislead into trying to use Office and SmartSuite applications they    don't have on their machine.

This list 412 is generated by a hidden ActiveX upload control 240,implemented by a DLL, which will be downloaded to client 102 only once.Once installed on the users machine, it will be able to determinequickly which Office and SmartSuite applications are installed on themachine by attempting to obtain a COM pointer to each application's OLEautomation server object. This pointer will only be obtainedsuccessfully if the application is installed.

The control 240 has no UI. It will be created without a window (or witha zero-size window) and will simply return information to the JavaScriptin the HTML scene.

Next, JavaScript in the scene will query the control for the list ofapplications, and generate the corresponding list 412 of radio button414 choices. Performance should not be an issue; the result will appearto be HTML that is “aware” of properties of the local machine.

-   2. User selects “Microsoft Word 2000 Page” 416 and clicks “Next . .    . ” 418. A new scene 420 appears in QuickPlace containing the upload    control—the control will display 422 a single Word.DOC file 424,    with no name and will also appear grayed out. At the same time,    Microsoft Word 2000 will be launched in the foreground, displaying a    new, empty Word document 426.

Since the edit scene 420 contains the upload control 422, it is loadedimmediately as the user enters the scene. The upload control will beprovided with the application chosen by the user, and will immediatelylaunch the application 426. It will also display a single file icon 424representing the file being created.

Word 2000 will be displayed in a separate window 426, allowing the userto use Word in the same manner as always.

-   3. User types in a new Word 2000 document, and then closes the Word    file 426, either using File->Exit, File->Close or File->Save As 428.    QuickPlace detects that the original Word document is no longer    being editing and brings the QuickPlace window 420 to the    foreground. The Word file is converted into HTML and displayed in    the upload control 422.

In accordance with the preferred embodiment of the invention, OLEautomation is used to determine whether or not the user is still editingthe new Word file 426. As the user is editing the document in Word, theQuickPlace upload control 240 will periodically query Word for the listof documents currently active. When the original document is no longeractive, QuickPlace knows that the user has finished his/her edits andthat it should import the file into QuickPlace 108. Any of these UIactions can finish the edit session on the original document:

-   -   File->Close: The user has closed the original file, but may        continue to use Word to edit other .DOC files.    -   File->Save As: The user has chosen to save the original file        with a new name on their local machine    -   File->Exit: The user has quit Word entirely.        Regardless of how the user finishes editing the document,        QuickPlace will detect that it is no longer active in Word. If        the file's contents have changed (i.e. it is not empty) the file        will be converted into HTML.

-   4. User publishes the page and the new .DOC file, along with its    equivalent HTML file, is uploaded to the server.

After the .DOC file is converted to HTML, it is uploaded to the server.The HTML and DOC files are both attached to the same Notes document, anda Notes field is set indicating to the QuickPlace JavaScript UI whichHTML was created.

Scenario 2: Import an Existing PowerPoint 97 File into QuickPlace.

-   1. User clicks “New . . . ” and then selects “Imported Page.” The    import scene with the upload control is displayed—this time the    control is initially empty.-   2. User selects an existing PowerPoint 97 (.PPT) file from the local    hard drive and drags/drops it into the upload control. A progress    dialog box appears displaying “Converting from Microsoft .PPT format    to HTML. Please Wait . . . ” Later, a PPT file icon is displayed in    the upload control. OLE automation converts the file into HTML and    imports it into QuickPlace.-   3. User publishes the page. The .PPT and all of its associated files    are uploaded to the server. The slides from the PowerPoint    presentation are all displayed in the same QuickPlace page, along    with “Previous,” “Next” and “Zoom” buttons. Referring to the UI of    FIG. 12, these slides are displayed in the same QuickPlace page.

Referring to FIG. 12, clicking the “Zoom” button 418 causes a separatebrowser window to appear with a larger version of the current slide; itwill also contain “Next” 423 and “Previous” 421 buttons. Displayingmultiple PowerPoint slides, Excel worksheets, or other data in the sameQuickPlace page is accomplished by uploading a series of HTML documents,one per slide/worksheet, to the same Notes document. In addition, eachof the HTML documents is modified to link to the next and previousdocument. When the user clicks on “Next” at read time, a URL is issuedto load the next slide in the page content frame as follows:“$FILE/slide5.htm?OpenElement”—referring to the next slide in thesequence. All images and other support files are attached to the sameNotes document as well.

Scenario 3: Edit Existing Microsoft Excel 97 Page.

-   1. User views Excel 97 page in QuickPlace and clicks “Edit . . . . ”    The edit scene with the upload control is displayed and the Excel 97    .XLS file is displayed as a file icon in the control. In addition,    Excel 97 is automatically launched with the user's original .XLS    file.

In accordance with a preferred embodiment of the invention, theassociated Office or SmartSuite application is automatically launchedand given the original file. This allows the user to edit the QuickPlacepage directly without having to double click on the file icon. It givesthe user the impression that she is directly editing the QuickPlacecontent using Excel 97, for example.

If Excel is not installed on the machine when this page is edited, forexample if a different user edited the page or the original user used adifferent machine, an error message appears informing the user thatMicrosoft Excel is required to edit the page. However, the edit scene isstill displayed with the XLS file icon—allowing the user to replace itwith a different Excel file if such a file were available.

-   2. User finishes editing the Excel XLS file, saves and exits Excel.    The XLS file is converted into HTML. Finally, the user publishes the    page and the new version of the XLS file, along with the HTML    equivalent, is uploaded to the server.

Implementing this feature is no different from the page creation scene,described above. The same code is used to detect when the user hasstopped editing the Excel 97 document, and to convert the XLS file intoHTML.

Scenario 4: Import and Edit an HTML File Originally Created by MicrosoftWord 2000.

One of the principal features of Microsoft Office 2000 is the ability tosave native Office documents, .DOC or .XLS files for example, as HTMLwithout losing any of the original formatting, layout or otherinformation specific to that Office application. For example, users cansave a Word 2000 document as HTML, and then later open that HTML fileusing Word and see the document in its original form, without losing anyfidelity along the way.

QuickPlace today allows users to import HTML files that were originallycreated by Office 2000, (Word, Excel or PowerPoint) into QuickPlace likeany other HTML file. However, in accordance with a preferred embodimentof the present invention, users may edit pages created by importing suchHTML files, using the Office application that originally created them.This scenario describes such an edit operation:

-   1. User creates a document using Word 2000, and then uses the Word    2000 “File->Save As Web Page” command to save the file.

Now the user has an HTML file on the local hard disk that contains thetext in HTML format, along with formatting information saved with XMLtags. In addition, Word has also created a number of support files, suchas images, an “XML file list” file, style sheets, and other files. Allof this information is used by Word to re-open the file later and obtainall of the original formatting and style information.

-   2. User imports this new HTML into QuickPlace, using the same import    UI.

In accordance with this embodiment of the invention, all of the supportfiles that were created by Word 2000, along with the HTML file, will bedetected and uploaded to QuickPlace. Previously, only the HTML and anyimages referenced by it were uploaded. Now, the HTML file is parsed todetermine whether it was created by an Office 2000 application. If itwas, all of the support files are located on the user's hard disk anduploaded to the server.

-   3. Later, user edits this imported QuickPlace page.

As soon as the user clicks “Edit,” QuickPlace displays the edit scenewith the HTML file's icon, and also automatically launch Word 2000 toedit the document. Even though the file was converted to HTML by Word,it will be displayed in its original form.

Once the HTML file was identified as a “Word 2000 HTML document” (step 2above) the Notes document corresponding to this QuickPlace page ismarked as containing a Word 2000 document, as if it were created usingthe New . . . , Microsoft Word 2000 Page UI described in Scenario #1.After the user clicks “Edit,” the HTML along with all of the supportingare downloaded to the user's machine. These files are placed in theuser's TEMP directory, but the support files are placed into asubdirectory corresponding to their original locations when the file wascreated. This facilitates Word 2000 reopening the file.

After the user makes some changes and closes in the file in Word 2000,the new version of the file along with all of the support files areagain uploaded to the server.

Scenario 5: Export an HTML Document Back to the User's Hard Disk in itsOriginal Form.

Previously, the user could import an HTML file into QuickPlace and allof the associated images would be uploaded to the server as well. Inaccordance with a preferred embodiment of the invention, the user maynow download the HTML and the images back to the hard disk—or to someother machine—in their original form.

-   1. User imports an HTML file into QuickPlace, which contains an    image.

As before, the HTML and the referenced image, are uploaded to theserver. In the background, the <img> tags in the HTML file are modifiedto refer to the copy of the image file attached to the Notes document onthe server. In accordance with this embodiment of the invention, theoriginal HTML file, i.e. an unmodified copy of the HTML file, isuploaded to the server as well.

-   2. User edits the imported page. The upload control is displayed    with the HTML and the image file. The user then drags and drops the    file onto the desktop.

In accordance with this embodiment of the invention, upload control 240downloads the unmodified, original copy of the HTML to the user'smachine, along with the image files that it refers to. Since all ofthese files are stored in the same directory on the user's machine, the<img> tags in the original HTML are modified again to reference theimage file in the same directory. This is necessary since the image filemay have originally been located in other directories on the user'smachine.

In accordance with this embodiment of the invention, users may create anew type of QuickPlace form based on a Microsoft Office or LotusSmartSuite document. For example:

-   1. User decides to create a new form: Customize->Forms->New Form-   2. Referring to FIG. 14, the “New Form” scene 430 appears. If    Microsoft Office or Lotus SmartSuite is installed on the user's    machine, an additional paragraph 432 is displayed “Based on a    Microsoft Office or Lotus SmartSuite Document”. This allows the user    to create a form based on a Word, Excel, or another Office or    SmartSuite document. When pages are created based on this form, the    corresponding application will be opened with a particular file. A    hidden ActiveX control returns whether any Office applications are    installed, or whether any SmartSuite applications are installed. If    none are, the upload control 434 and its introduction text 432 are    displayed.-   3. User selects an Excel 2000 file 436 and drops it into the upload    434 control that appears below the “Based on a Microsoft Office or    Lotus SmartSuite Document” paragraph 432.

This file, represented by icon 436, is uploaded to the server—this willform the basis for this form. Every user who creates a page based onthis form will see Microsoft Excel opened and loaded with this file.

-   4. The user adds some additional fields 440-446 and then saves the    form by clicking “done” 448.-   5. Later, the user creates a page based on this new form: “New . . .    ”, select the form, etc. As soon as the user starts to edit the new    page, Microsoft Excel is launched with the file that was originally    attached to the form. This allows every user to enter information    into a spreadsheet, for example. It's essentially the same as    creating a page based on an Excel spreadsheet, except that Excel is    pre-loaded with a file selected by whichever user created the form.    If a particular user doesn't have Excel installed on her machine,    she'll receive an error message informing her that Excel is required    to create a page using the form.-   6. After the user closes the Excel file, it is converted to HTML and    uploaded to the server. The user may then enter values into other    fields on the form and publish the page. Once the page is published,    it is considered to be based on the Excel document—whenever it is    edited in the future, Excel is again automatically launched with the    given file.    Scenario 7: Create and Use a Form Containing a Non-Empty File    Attachment Field.

Previously, the “Attachments” field in QuickPlace could be added toQuickPlace forms to allow users to attach documents to pages createdusing a form. However, the attachment always appeared empty for each newpage. In accordance with a preferred embodiment of the invention, theform creator may attach a file or set of files to this field which willappear pre-attached to each page created using the form. For example:

-   1. User creates a new form. Customize->Forms->New Form-   2. User adds an “Attachments” field, by clicking the “Add”button,    selecting “Attachments,” and clicking “Next.” The “Attachment    Options” scene appears. Previously, the attachment options scene was    empty. Referring to FIG. 15, in accordance with this embodiment of    the invention, an upload control scene 450 is displayed. The user    then may attach any set of files to the form, which will then be    attached automatically to each page created based on that form.-   3. User drops a Word document 452 into the upload control 434. Then    the user saves the new field and the form—call it “Word Form.” The    Word document 452 will be uploaded and attached to the Notes    document representing the QuickPlace form like any QuickPlace page.-   4. Later, another user creates a page based on this new form: “New .    . . ” and “Word Form.” An edit scene appears containing an upload    control; the original Word document is displayed in the upload    control.

Importing Additional File Formats Using an HTML Export Engine

Referring to FIG. 16, in accordance with an exemplary embodiment of theinvention, to allow browser 112 users to import interest content into aQuickPlace, HTML conversion module 454, such as an “HTML Export” enginefrom Verity, is used on the server. Whenever a browser 112, such asNetscape, user imports a file—or when an Internet Explorer user importsa file that is not recognized by the OLE automation code describedabove, i.e. a non-Office/SmartSuite file—as is represented by line 455,the file is uploaded unmodified to the server. As is represented by line451, server 100 passes the file onto the Verify engine 454, which willattempt to convert it into HTML. If this is successful, as isrepresented by line 453, the HTML will then be attached to theQuickPlace page and displayed whenever a user reads this page.

Scenario #8: Netscape User Imports Microsoft Word document intoQuickPlace

The sequence of events that will occur when a Netscape user attempts toimport a Microsoft Word document into QuickPlace are as follows:

-   1. Netscape user creates an imported page in QuickPlace: New . . . ,    Imported Page.-   2. The user selects a Microsoft Word document from the hard drive    using the standard HTML “Browse” button and the standard File-Open    dialog box.

Previously, every file imported by the user was assumed to be HTML. Inaccordance with this embodiment of the invention, the user will be ableto select any file, as long as it is supported by the conversion engine454. For example, for a Verity conversion engine, formats that aresupported include:

Microsoft Word 97/2000

Microsoft Word 6/95

Microsoft Word 2

Microsoft Word Mac

Microsoft Excel

Microsoft PowerPoint 97/2000

Microsoft PowerPoint 95

Microsoft PowerPoint 4.0

Microsoft Write

Microsoft Rich Text Format

Lotus WordPro

Lotus 123 96/97

Lotus 123 V2-5

Lotus Freelance Graphics 2.x

Lotus Freelance Graphics 96/97

Lotus AmiPro

Corel Quattro Pro Spreadsheet

Corel WordPerfect 5.1

Corel WordPerfect 6.x to 8.x

Windows Bitmap

Icon Files

PNG (Portable Network Graphics)

TIFF

-   3. User clicks “Next”

At this point, Netscape will automatically upload the selected file tothe server. If the user picked a file which is not supported by Verity,a JavaScript error would be displayed.

In addition to uploading the selected file, the “h_command” HTML fieldis set to a value such as “h_VerityImport”—this will cause the VerityImport command to be executed on the server. This code will then obtainthe selected file from the browser's HTTP Post request, save it in theTEMP directory on the server machine, and then call the Verity HTMLExport engine.

If the Verity code is able to successfully convert the selected file toHTML, the server attaches the resulting HTML file, and any support imagefiles or other files, to the current Notes document. Finally, thedocument is published as usual.

If the Verity code 454 is unable to convert the selected file to HTML, aserver exception will be thrown, and a helpful error message displayedin the user's Netscape browser 12.

To implement this embodiment of the invention, a new “Haiku Command”(“h_VerityImport”) in NINOTES.DLL is implemented to call into Verity 454when a file is received from the browser 112. This command calls intothe Verity C API, passing the uploaded file 451 as a parameter. Inaddition, some of the HTML import code is copied into the server(NINOTES.DLL) to alter the HTML after it has been created byVerity—fixing up image tags, and adding JavaScript to the HTML to makeit function properly inside of QuickPlace.

Scenario #9: Editing a QuickPlace File Attachment: for Example“schedule.xls”

Referring to FIG. 17 through FIG. 24, in accordance with a preferredembodiment of the invention, editing a QuickPlace file attachment andsaving the changes back to QuickPlace will occur as follows:

-   1. User reads a QuickPlace page which contains 3 file attachments    458, one of which is called “schedule.xls.” 456. The file is    displayed inside a grayed-out upload control 460. The grayed-out    appearance of the upload control 460 reminds the user that this is a    read-only copy of the file, and that if the user attempts to modify    the file here it will not be possible to save the new version of the    file back into QuickPlace.-   2. The user edits the QuickPlace page and double clicks on    schedule.xls 456, launching Excel 2000, the associated application.    This time, in edit mode, the upload control 462 is not grayed out    and the user realizes that the file may be edited.-   3. The user makes some changes to the file and shuts down    Excel 2000. QuickPlace detects that Excel 2000 is no longer running,    determines that schedule.xls 456 has been modified and displays    dialog box 464. If the user clicks “Yes” 466 the new version of    schedule.xls is uploaded to the server and the old version is    discarded. However, if the user clicks no 468, an additional file    icon 470 appears in the upload control 462. The user must type in a    new name for this file—or type “Escape” and cancel the upload    operation. Finally, if the user doesn't select a new file name and    simply presses “ENTER” an error is displayed.

File System Directory Architecture

In accordance with the preferred embodiment of the invention, every newQuickPlace created gets its own directory under the QuickPlace masterdirectory. The name of that directory is same as the name of theQuickPlace. Each additional room in the QuickPlace is another file(.nsf) in the QuickPlace directory. During the QuickPlace serverinstallation, the default QuickPlace (also called the “Welcome”QuickPlace) with the name of QuickPlace is automatically created. Thisis the entry point to the QuickPlace server including the serveradministration. FIG. 8 shows the directory structure, along with thefiles in “Welcome” QuickPlace, in a stand-alone QuickPlace server.

For example if Millennia is the a current QuickPlace, then the basicinfrastructure of the Millennia QuickPlace resides under

\lotus\domino\data\quickplace\millennia

(on Domino server—given that

\lotus\domino\data

is the data directory) or

\lotus\quickplace\data\quickplace\millennia

(on stand-alone—given that

\lotus\quickplace

is the QuickPlace installation directory).

When QuickPlace server is installed, the “Welcome” region or the“Administrator's Place” is pre-configured to allow an entry point to theQuickPlace server. An administrator can then administer the newlyinstalled QuickPlace server from this entry point. This so calledadministrative QuickPlace resides under the QuickPlace directory whichin turn is under the data directory. For an example it is

c:\lotus\domino\data\QuickPlace\QuickPlace

when installed under Domino, and

c:\lotus\QuickPlace\data\QuickPlace

when in stand-alone mode. It contains the following files: Main.nsf,Contacts1.nsf, CreateHaiku.nsf, Admin.nsf. The templates for theseDomino databases reside in the directory named AreaTypes. The “Welcome”page may be configured to suit the needs of an organization.

TASKS

In accordance with a preferred embodiment of the invention, custom fielddefinitions allow a user to create forms in the QP environment withouthaving to write HTML, leaving the generation of the HTML to QuickPlace.A field object may be created at the browser in Java script thatcontains the properties of the field and the methods which display andoperate on that field, including validation. In general, an object ismade up of properties and methods. Previously, the HTML was stored withthe field definitions. A problem with this procedure is that when it isdesired to change the field, it was necessary to upgrade the data in allof the field definition documents. With the present invention, users cannow create their own field definitions. The html is generated on thefly, and this facilitates the creation of tasks.

When a new form is created, all fields that go with that form areobtained. A manager can create a form. A page is something that containsdata. A form is use to create that data. When anyone creates a page, heis presented a list of possible forms. A manager can request creation ofa new form. When a new form is requested, QP shows a form that showsinformation that is need to create the form. The user fills in thatinformation, and can also click an add field button. QuickPlace respondswith a list of the field types that can be created. The user selects andconfigures the desired field type for each field desired on the form.When the user done adding fields, he clicks “done”. Thereafter, when auser clicks new, that new form is displayed as one of the options foruser selection.

Prevously, very difficult to create new types of fields. In accordancewith the present embodiment of the invention, a task page is displayedat the browser together with an edit page and fields for all of thematerial needed to create a field.

Further in accordance with a preferred embodiment of the invention, atask control section is provided which can be added to any new form,thus enabling task definitions in collaboration space. Task is an optionwhen adding a new field, and this can be customized to include a startdate and whether it will have a priority or category, and default valuefor the priority.

QP client code implements the “on the fly” concept. The code is storedon the server, and sent to the client for the creation of these fields,and the corresponding HTML executes on the client. A page on the serveris sent to the client, that page contains the java script which willgenerate the HTML.

Referring to FIG. 23, in accordance with a preferred embodiment of theinvention, users in collaboration space can view a tasks page 506 as atimeline 508, with options for refining the timeline display for thevariety of timescales (days, weeks, months, quarters, etc.) that mayarise. Also, referring to FIG. 22, tasks page 506 may be presented inlist mode, with the user provided buttons 508 for selecting a desiredformat, and other options 510. FIG. 24 represents a read scene statedisplay for tasks.

Forms Definition in Collaboration Space

In accordance with a preferred embodiment of the invention, users areprovided with a method for defining forms to create pages withincollaboration space. These methods include options to upload a documentand send a notification, add a meeting to the calendar, or add a taskinto the QuickPlace.

By clicking on New . . . , the user gets a list of forms included inQuickPlace that can be used to add a new document to it. The formsprovided are sufficient for many uses, but do not give any task-specificways of adding content to the QuickPlace. To do this, a user may createher own form and adapt it to her particular needs.

There are three ways to create forms: create a form using standardQuickPlace fields; import a form 250 created in Microsoft Office 228;and import a form 122 created in an HTML editor 124.

In accordance with this embodiment of the invention, when creating aform, it can be adapted to the workflow in the team.

Defining a Type of Workflow

To accomplish a company's goals, certain tasks must be executed,fulfilling a number of activities in a certain order, and doing thiswithin a given time frame. This definition of goals and procedures theworkflow of an organization. In accordance with a preferred embodimentof the invention, collaboration space can be adapted to reflectworkflow.

Referring to FIG. 25, workflow page 512 provided by QuickPlace enablesintegration of a form into the organization's workflow. The followingoptions are available from the form workflow page:

-   -   No special workflow 514: pages are simply created by an author        and published by the member who created the page.    -   Simple Submit 515: pages are simply created by an author and        submitted. This will add a submit button to the button bar at        the top of the page.    -   Editor In Chief 516: pages are created by authors, but pages        will only be published after being approved by a specific        member—the Editor In Chief.    -   Approval Cycle 517: each page is routed through a series of        members in a specific order.    -   Multiple Editors 518: pages are created by an author and then,        once published, can be further edited by any of the authors in        the room.        No Special Workflow

The no special workflow option 514 allows members to publish their pagesbases on this form without first getting approval from any other memberof the QuickPlace either as a draft or in their final form.

Simple Submit

The simple submit option 515 is chosen when the pages created by thisform don't have to undergo review, the users are not able to save pagescreated by this form as drafts and when it is needed to be able torename the Publish button. When an author creates a page using thisform, the following events happen, assuming that the Simple submitworkflow was used to rename the Publish button to Post to ProjectMilestones button.

-   1. The author creates the page and clicks on Post to Project    Milestones.-   2. The page is published to the Project Milestones folder.    Editor in Chief

The editor in chief option 516 is selected when a single member is toreview each page created with the form. When an author creates a pagethat has to be reviewed by an Editor in Chief, the following eventoccurs:

-   1. The author finished editing the page and notifies the Editor in    Chief that the page is ready for review by clicking on the Submit    button. Technically, the author has passed the right to edit the    page to the Editor in Chief. Editor-In-Chief Pages are created by    authors, but pages will only be published after being approved by a    specific member—the Editor-In-Chief.    -   Upon submitting the page, the author can choose to send the        Editor in Chief a note about the page by E-mail. The note only        appears in the E-mail message, not on the page itself.    -   The author can also save the page under construction to continue        editing at a later time before submitting it to the Editor in        Chief.-   2. The Editor in Chief receives an E-mail message containing the    author's note (if one has been created) with a link to the new page.-   3. The Editor in Chief reviews the pages and does one of the    following:    -   Edits the page (if necessary) and by publishing approves it. The        Editor in Chief can select to notify the author that the page        has been published.    -   Rejects the page. The Editor in Chief can choose to attach a        note to the rejection message. The author receives an E-mail        message saying that either the page has been published or        rejected. If the pages has been rejected, the author can revise        the page and then resubmits it to the Editor in Chief for        approval.        Approval Cycle

The approval cycle option 517 is selected when each page is to be routedthrough a series of members in a specific order. This workflow option517 is chosen when the more that one member of the collaboration spaceis to review pages created with the form. This is similar to the Editorin Chief process 516, only that it includes more that one reviewer.

After choosing approval cycle, which members and in which order toreview the document are specified. Restrictions may be set on who mayread or edit the final page and the member determined who is responsiblefor editing the page when it is rejected. By way of example, if anapproval cycle 517 is defined with two reviewers, and the folder ProjectMilestones set as the destination for final approved pages, thefollowing events occur:

-   1. The author finishes editing the page and notifies the first    reviewer that it can be reviewed by clicking the Submit button.    -   The author can choose to send a note on the page in an E-mail        message to the first reviewer. This note only appears in the        E-mail message, not the page itself.    -   The author can also choose to save the page under construction        to continue editing it at a later time.-   2. The first reviewer receives an E-mail notifying him that the page    is ready for review. It contains the note from the author (if one    was created) and a link to the page awaiting approval. The first    reviewer reviews the page and takes one of the two following    actions:    -   Reads and edits the page (if necessary) and submits it to the        next reviewer.    -   Rejects the page. The reviewer can choose to create a note to        accompany the rejection notice.-   3. If the first reviewer rejects the page, the author receives an    E-mail notifying him of the rejection. He then can change the page    and resubmit it to the first reviewer, repeating the first two steps    of this procedure.-   4. If the first reviewer approves the page, the second reviewer    receives an E-mail with a link to the page awaiting approval and a    note from the first reviewer (if one was created). The reviewer    takes one of the following actions:    -   Reviews, edits (if necessary) and approves the page. The page is        then published in the Project Milestones folder.    -   Rejects the page. The author receives an E-mail message stating        that the page has been rejected. The second reviewer can choose        to create a note to accompany the notification.-   5. The author receives the notification, corrects the page and    resubmits it to the second reviewer, who in turn can then either    reject it again or publish it.    Multiple Editors

The multiple editors option 518 is selected when pages are created by anauthor and then, once published, can be further edited by any otherauthor in the room. This option is chosen when all authors in theQuickPlace are given edit rights to the page created by this form. Thisis useful if a document has to be viewed by all and all authors may addtheir thoughts to it. This option is useful for poll forms, as a useredits the page when she casts a vote in the poll. The member has to bean author to take part in the voting.

Creating a Form Using Standard QuickPlace Fields

Creating a form within QuickPlace may be done in several ways. Togenerate a simple form with just a couple of fields in it, use thefeature within QuickPlace. If designing a form that is moresophisticated, or it is needed to include JavaScript to do checks onfields, for example, the form is created outside of QuickPlace andimported, as illustrated in FIG. 21.

By way of example, suppose users are to be able to add events to thecalendar when the page is published, and also have the pages publishedin a specific folder. To do this, choose customize from the main menu,and click on new form. On the next screen, choose simple form and clickon Next. FIG. 26 illustrates the Edit form page 522. Add fields to theform by clicking on Add 520, and select a field. To add the page createdby this form to the calendar automatically, choose the field Event dateand time. As shown in Table 52, QuickPlace responds providing a choiceof standard fields which can be used to create the form. Furthermore,referring to Table 53, there are a number of fields that arenon-editable, but provide additional information on the form.

TABLE 52 EDITABLE FIELDS FOR CREATE FIELD Field type Function Plain TextPresents a one-line unformatted text field Text Area Presents amulti-line unformatted text field Pop-up list Presents a list of choicesfrom which to choose Time Pop-up Presents a time pop-up Name Pop-upPresents a list of QuickPlace members Attachments Presents a field foradding file attachments Rich Text Presents a field where the author canenter formatted text and images Calendar Date-Time Presents acombination of date and time fields so that pages created with this formwill automatically be added to this QuickPlace's Calendar Task Presentsa combination of task related fields so that pages created with thisform can be tracked as tasks

TABLE 53 NON-EDITABLE FIELDS FOR CREATE FORM Field type FunctionNotification Indicator Used to automatically send E-mail to individualsNon-Editable Rich Text Presents non-editable text and graphics on theform. Typically this is used to provide an attractive banner on top ofthe form Page Author Presents the non-editable name of the author whocreated the page with this form Creation Date Presents the non-editabledate that the page was created Last Modified Date Presents thenon-editable last modification date of the page Page Size Presents thenon-editable size of the page Serial Number Presents a non-editableunique for each page created with the form (for example, Purchase OrderNumber)

Selecting a field type brings up on the screen the instructions foradding to the field to the form being developed. If the pages created bythis form are to be published in a specific folder, the folder is chosenfrom a drop-down list. As an option, a fuller description of what theform does can be added. This description appears next to the name of theform when the user clicks on New . . . .

Setting Tasks

Besides choosing a type of workflow for forms created in a QuickPlace,task settings may be chosen on the pages that are created using the formand adding them to the Tasks list in the QuickPlace. To do this, add thefield Task from the Add Field page and click Next. The following pageprovides a way to name the task field, set a start date and the priorityfor the task, and set the initial choice for the priority. When finishedadding fields to the form, clicking on Done saves the form.

Authors can create pages based on the form by clicking New . . . in thebutton bar and selecting the form from the page which appears next.

Upload a Form Created in MS Office

If the form requires some fields that are not part of the QuickPlaceform creation applet, a form can be created either in MS Office 228 orin an HTML editor 124. To use MS office 228, create a new Word document,and add web form fields, such as by clicking on the appropriate fieldicon in a Microsoft Word web tools toolbar. Save the document as a Wordfile 250 when finished. QuickPlace will automatically convert thedocument to HTML when it is imported.

The web tools toolbar in Word offers eleven standard fields to use in adocument: Checkbox control, Option or Radio button control, Drop Downbox control, Listbox control, Textbox control, Text Area control, Submitcontrol, Submit with Image control, Reset control, Hidden control, andPassword control.

By selecting control and clicking on Properties, an HTML name and valuecan be assigned to the field.

ActiveX Controls

ActiveX controls, supported by Internet Explorer, may also be added fromthe control toolbox and clicking on Properties. The following ActiveXcontrols are available from the tool box: Check box, Spin button, Scrollbar, Label, Text box, Command button, Option or Radio button, List box,Combo box, Toggle button, Image. Additional ActiveX controls can beregistered by clicking on More Controls and registering the ones needed.When finished editing the document, it is saved as a MS Word document250 and upload it to the QuickPlace. To upload, click on Customize andselect Form. On the next page, click on New form, and select MicrosoftOffice form, then click on Next. Referring to FIG. 27, this next page isshown. The MS Word document can by uploaded by dragging and dropping itinto the bucket (upload control 240), or selected by clicking on Browse524. A workflow option can be selected from list 526. To change thestandard Publish button for the form, select Workflow 526 and chooseSimple submit 515. This will add a submit button into the button bar atthe top of form when it is filled in. Click on Next and provide a name528 for the submit control on the next page. Click on Next. Select thefolder the pages are to be published in from the drop-down list 444. Adda short description of the form, if desire, at field 446. Clicking onDone will publish the form to the QuickPlace.

Authors can publish pages by selecting New . . . from the button bar andselecting the form created from the list.

Upload a Manually Created HTML Form

If more control over how the form appears in the QuickPlace, or ifJavaScript must be included, the form is created using an HTML editor124.

The following two examples illustrate how this is to be done. Whencreating an HTML form manually in an HTML editor 124:

-   (1) Put all code, including any JavaScript, within the <body> tag of    the document. All other parts of the document, that is, the <head>    and <title> tags, will be replaced by custom QuickPlace tags once    the form is uploaded.-   (2) The form tags <form> and </form> are not needed within the    manually created HTML form. QuickPlace will add custom code when the    form is uploaded.-   (3) QuickPlace system fields can be used in the form. In the    following examples, the name of the page is set in a text field    named h_Name, which is the system field for the page title.    Use QuickPlace Controls in the Form

QuickPlace provides two client-side components for users to quicklyinteract with the QuickPlace, the Rich text and the Upload control.Authors can format their text in the Rich text control, giving it apersonal look and feel. They can upload documents to the QuickPlace bydragging and dropping 111 them into the Upload control 240. Thesecontrols only have their full functionality in Internet Explorer. Bothare ActiveX controls in Internet Explorer. Calling a form with the Richtext control included starts a Java applet in Netscape Navigator. TheUpload control displays a browse button in Netscape Navigator. Theauthor then can select a file from his computer when he or she clicks onit.

Both browsers display the formatted Rich text in read mode and load theappropriate client-side component when changing into edit mode. InternetExplorer lets the user drag a document out of the Upload control box 240to download or view the document, whereas Netscape Navigator displays alink the user can click on to download or view the file. The formsprovided by QuickPlace use these controls, and they can be include newforms.

The QuickPlace Upload Control Example

The example form of Table 54 creates a page that includes the QuickPlacecontrol to upload files to the QuickPlace. It also includes some fieldsfor the user to fill in to provide information about the attached file.The <body> tag contains the complete form, and the <form> tags areomitted from the HTML page. Adding fields begins right after the <body>tag. Standard HTML fields can be used in the form, and this examplesshows use of text fields, a text area and a drop-down field.

TABLE 54 PAGE UPLOAD CONTROL <html> <head> <title>Upload control</title></head> <body> <table border=0> <tr> <td colspan=3><imgsrc=“ecblank.gif” width=“300” height=“1” border=“0”> <tr><td><b>Document Title</b></td> <td>&nbsp;</td> <td><b><input type=“text”name=“h_Name”></b></td> </tr> <tr> <td>Your first name</td> <td>&nbsp;</td> <td><input type=“text” name=“fname” </td> </tr> <tr> <td>Your lastname</td> <td>&nbsp; </td> <td><input type=“text” name=“lname”</td></tr> <tr> <td>Company</td> <td>&nbsp; </td> <td> <selectname=“selector”> <option value=“ -- choose one --”>----choose one----</option> <option value=“Millenia”>Millenia</option> <optionvalue=“TheRock”>TheRock</option> <option value=“CapMan”>CapMan</option></select> </td> </tr>In the continuation of Table 54, the QuickPlace component for the Uploadcontrol is included. In Internet Explorer, this tag will include theActiveX Upload control in the page, and a browse button in NetscapeNavigator. In the published page, the button converts to a link to thepage in Netscape Navigator, while the Internet Explorer displays theActiveX Upload control.

TABLE 54 (CON'T.): PAGE UPLOAD CONTROL <tr> <td valign=“top”>Give ashort description<br>of your file</td> <td>&nbsp;</td> <td><textareaname=“description” rows=5 cols=50></textarea></td> </tr> <tr> <tdvalign=“top”>place your file here</td> <td>&nbsp;</td> <tdvalign=“top”><QuickPlaceCONTROL type=“attachment” name=“attachment”></td> </tr> </table> </body> </html>The QuickPlace Upload control can be used in any manually created HTMLform 122.The QuickPlace Rich Text Control

The example form of Table 55 creates a page that includes the QuickPlaceRich text control to add Rich text and graphic text to the page. Richtext is formatted by adding the appropriate HTML tag around it. Todisplay the graphic text, QuickPlace uses its built-in graphics server.The <body> tag contains the complete form, and the <form> tags areomitted from the HTML page. Fields are added right after the <body> tag.Standard HTML fields can be used for the form, this example uses textfields and a drop-down field.

TABLE 55 QuickPlace RICH TEXT CONTROL EXAMPLE <html> <head><title>Upload control</title> </head> <body> <table> <tr> <tdcolspan=“3”><IMG src=“ecblank.gif” height=“5” width=“200” border=“0”></td> </tr> <tr> <td><b>Document Title</b></td> <td>&nbsp;</td><td><b><input type=“text” name=“h_Name”></b></td> </tr> <tr> <td>Yourfirst name</td> <td>&nbsp; </td> <td><input type=“text”name=“fname”</td> </tr> <tr> <td>Your last name</td> <td>&nbsp; </td><td><input type=“text” name=“lname”</td> </tr> <tr> <td>Company</td><td>&nbsp; </td> <td> <select name=“selector”> <option value=”-- chooseone --”>----choose one ----</option> <optionvalue=“Millenia”>Millenia</option> <optionvalue=“TheRock”>TheRock</option> <option value=“CapMan”>CapMan</option></select> </td> </tr>In the continuation of Table 55, the QuickPlace component is includedfor the Rich text control. In Internet Explorer, this tag will includethe ActiveX Upload control in the new page, and a Java applet inNetscape Navigator. Both browsers display the Rich text within therelevant HTML tag. To display the graphic text, QuickPlace uses Limerickin both browsers.

TABLE 55 (CON'T.): QuickPlace RICH TEXT CONTROL EXAMPLE <tr> <tdvalign=“top”>&nbsp;</td> <tr> <td>&nbsp;</td> <td>&nbsp;</td><td><QUICKPLACECONTROL type= “richtext” name=“richtext”<>/td </tr></table> </body> </html>

QuickPlace Specific JavaScript Functions

Two QuickPlace specific JavaScript functions to use with forms exist inQuickPlace. They are event handlers that can be called when the form isloaded from or a page created by the form is submitted to theQuickPlace.

QDK_HTML_FormOnLoadHandlerCallback (theForm)

This JavaScript function is called when the form loaded from theQuickPlace. It can, for example, set certain default field values. Theexample of Table 56 sets the expiration date for a page created withthis form to two months.

TABLE 56 FORM ON LOAD HANDLER functionQDK_HTMLForm_OnLoadHandlerCallback( theForm) { if ( h_IsNewDoc == ‘1’) {var now = new Date ( ); now.setMonth ( now.getMonth ( ) + 2); varexpirationDate = now.toLocaleString ( ); expirationDate =expirationDate.substr( 0, expirationDate.indexOf ( ‘ ’));theForm.expires.value = expirationDate; } theForm.h_Name.focus( ); }QDK_HTML_FormOnSubmitHandlerCallback ( theForm)

The JavaScript function of Table 57 is called when the form is loadedfrom the QuickPlace. It can, for example, check if the user has entereddata into fields that have to be filled. This example checks if a properE-mail address has been entered by checking for the @ symbol and a dotin the string following it:

TABLE 57 HANDLER CALL BACK functionQDK_HTMLForm_OnSubmitHandlerCallback( theForm) { var isOk = false; if (theForm.email.value.indexOf( ‘@’) > 0 && theForm.email.value.indexOf(‘.’) > 2) { isOk = true; } else { alert( ‘Please enter a valid emailaddress’); } return isOk; }These functions are very handy to perform checks or changes whileloading forms or publishing pages based on forms. They can be adapted toperform whatever check is needed for a forms.

Advantages Over the Prior Art

It is an advantage of the invention that there is provided acollaboration space application model for creating web applications thatare aesthetically pleasing and present the user with a simple interface.

It is an advantage of the invention that there is provided a system andmethod for creating web applications that are instantly created,instantly archived, team and project oriented, easy to use, created,accessed and administered via the Web, reusable, and extensible.

It is an advantage of the invention that there is provided an improvedmethod and system for uploading Microsoft Office documents,presentations and sheets into a place in collaboration space.

Alternative Embodiments

It will be appreciated that, although specific embodiments of theinvention have been described herein for purposes of illustration,various modifications may be made without departing from the spirit andscope of the invention. In particular, it is within the scope of theinvention to provide a computer program product or program element, or aprogram storage or memory device such as a solid or fluid transmissionmedium, magnetic or optical wire, tape or disc, or the like, for storingsignals readable by a machine, for controlling the operation of acomputer according to the method of the invention and/or to structureits components in accordance with the system of the invention.

Further, each step of the method may be executed on any generalcomputer, such as an IBM System 390, AS/400, PC or the like and pursuantto one or more, or a part of one or more, program elements, modules orobjects generated from any programming language, such as C++, Java,Pl/1, Fortran or the like. And still further, each said step, or a fileor object or the like implementing each said step, may be executed byspecial purpose hardware or a circuit module designed for that purpose.

Accordingly, the scope of protection of this invention is limited onlyby the following claims and their equivalents.

1. Method for integrating first and second desktop models by importingand publishing documents generated by a content creation and editinginterface tool of said first model including a coordinated suite ofoffice applications having word processor, spreadsheet and databaseapplications in a place in collaboration space in accordance with saidsecond model including room, folders, and panes, comprising: creating adocument file in said first desktop model using said interface tool;opening in a browser a place in collaboration space; placing saiddocument file into said place; automatically converting said document toa hypertext markup language (html) file; and saving said document fileand said html file on a page in collaboration space of said seconddesktop model with said html file displayed in said place in read modeand said document file displayed in said place in edit mode.
 2. Themethod of claim 1, further comprising the steps of: at said browser,dragging and dropping said document file into said place as a templatefile; and creating from said template tile a form.
 3. The method ofclaim 2, further comprising the steps of: using said form to create anew document of said first model.
 4. Method for uploading a documentprepared by a content creation and editing interface tool of a firstmodel including a coordinated suite of office applications having wordprocessor, spreadsheet and database applications into a place incollaboration space organized in accordance with a second modelincluding room, folders, and pages, comprising the steps of: creating adocument file including web form fields using said interface tool ofsaid first model; saving said document file; opening in a browser aplace in collaboration space; importing said document file to saidplace; upon importing said document into said place, automaticallyconverting said document into a web file containing hyperlinks thatpoint to web pages.
 5. The method of claim 4, said web file being ahypertext markup language (html) file.
 6. The method of claim 5,including the step of including web form fields in said document file byselecting field icons from a web tools toolbar.
 7. The method of claim6, said toolbar including checkbox control, option or radio buttoncontrol, drop down box control, listbox control, textbox control, textarea control, submit control, submit with image control, reset control,hidden control, and password control.
 8. Method for importing a documentfile into a place in collaboration space organized with rooms, folders,and pages according to a second model, comprising the steps of: creatingsaid document file using a content creation and editing interface toolof a first model including a coordinated suite of office applications;presenting at a browser an interface window to said place including anew selector; responsive to user selection of said new selector and animport option, displaying an import scene with an empty upload control;dragging and dropping said document file to said upload control in abrowser rendition of said place in collaboration space; and responsiveto receiving said document file in said upload control, automaticallyconverting said document file to hypertext files; displaying a documentfile icon in said upload control; and importing said hypertext filesinto said place.
 9. The method of claim 8, further comprising the steps:responsive to said user publishing said document file to saidcollaboration space, uploading to a collaboration space server saiddocument file and said hypertext files.
 10. The method of claim 9, saiddocument file being a presentation file comprising a plurality ofslides.
 11. The method of claim 10, further comprising the steps of:displaying said slides in a same page together with previous, next, andzoom buttons.
 12. The method of claim 11, further comprising the stepof, responsive to selection of said zoom button, displaying a largerversion of a current slide also including next and previous buttons. 13.The method of claim 11, said hypertext files being hypertext markuplanguage (html) files.
 14. The method of claim 9, further comprising thesteps of: preparing to display a plurality of data objects contained insaid document file by: preparing and importing into a common page atsaid place a separate hypertext file for each said data object, togetherwith any included images and support files, modifying said hypertextfiles to link to next and previous data objects within said documentfile; and at read time, responsive to user selection of said next orprevious control, issuing a uniform resource locator (url) to load anddisplay a respective next or previous data object in sequence.
 15. Themethod of claim 14, said data objects being presentation slides orspreadsheet worksheets.
 16. The method of claim 15, said hypertext filesbeing hypertext markup language (html) files.
 17. A system for uploadinga document into a place in collaboration space organized according to asecond model including room, folders, and pages, comprising: a contentcreation and editing interface tool of a first model including acoordinated suite of office applications having word processor,spreadsheet and database applications for creating a document fileincluding web form fields; a browser for rendering a place incollaboration space; a storage device for saving said document file; anupload control for importing said document file to said place; a serverfor implementing said second model and automatically, upon importingsaid document into said place rendered in said browser, for convertingsaid document into a web file containing hyperlinks that point to webpages.
 18. A system for importing a document file generated using acontent creation and editing interface tool of a first model including acoordinated suite of office applications having word processor,spreadsheet and database applications into a place in collaborationspace organized in accordance with a second model including room,folders, and pages, comprising: a browser interface window to said placeincluding a new selector; a storage for storing said document file; animport scene; an upload control; said import scene being responsive touser selection of said new selector and an import option for displayingsaid upload control; dragging and dropping said document file from saidstorage to said upload control in said place as rendered in saidbrowser; and said upload control being responsive to receiving saiddocument file for, automatically converting said document file tohypertext files; displaying a document file icon in said upload control;and importing said hypertext files into said place.
 19. A programstorage device readable by a machine, tangibly embodying a program ofinstructions executable by a machine to perform method steps foruploading a document generated by a content and editing interface toolof a first model including a coordinated suite of office applicationshaving word processor, spreadsheet and database applications into aplace in collaboration space organized in accordance with a second modelincluding room, folders, and pages, said method steps comprising:creating a document file using said content and editing interface toolincluding web form fields; opening in a browser a place in collaborationspace; saving said document file; importing said document file into abrowser rendition of said place; upon importing said document into saidplace, automatically converting said document into a web file containinghyperlinks that point to web pages.
 20. A program storage devicereadable by a machine, tangibly embodying a program of instructionsexecutable by a machine to perform method steps for importing a documentfile generated by a content creation and editing interface tool of afirst model including a coordinated suite of office applications into aplace in collaboration space organized according to a second modelincluding room, folders, and pages, said method steps comprising:presenting at a browser an interface window to said place including anew selector; responsive to user selection of said new selector and animport option, displaying an import scene with an empty upload control;dragging and dropping said document file to said upload control; andresponsive to receiving said document file in said upload control,automatically converting said document file to hypertext files;displaying a document file icon in said upload control; and importingsaid hypertext files into said place.
 21. A computer program product orcomputer program element for uploading a document prepared by a contentcreation and editing interface tool of a first model including acoordinated suite of office applications into a place in collaborationspace organized in according to a second model including room, folders,and pages, according to the steps of: creating a document file usingsaid interface tool including web form fields; opening in a browser abrowser rendition of a place in collaboration space; saving saiddocument file; importing said document file to said browser rendition ofsaid place; upon importing said document into said place, automaticallyconverting said document into a web file containing hyperlinks thatpoint to web pages.